Create hub certificates
post
https://{your_site_interface}/opa-hub/api/12.2.40/hubCertificates
This operation will create one or more hub certificates
Request
There are no request parameters for this operation.
Supported Media Types
- application/json
Nested Schema : hubCertificatePost
Type:
Show Source
object-
keyId(required): string
The key id
-
privateKeyPemData(required): string
The private key details
-
x5cPemData(required): string
The certificate details
Security
-
Authorization: apiKey
Type:
apiKeyDescription:Obtain a bearer token from https://{your_site_interface}/opa-hub/api/12.2.17/auth and use it in the Authorization header as: Bearer {token}. -
oauth2_opa: oauth2
Type:
oauth2Description:POST the OAuth2 Client Credentials parameters to https://{your_site_interface}/opa-hub/api/12.2.17/auth and use the access token from the response in the Authorization header.
Response
Supported Media Types
- application/json
201 Response
The request has been fulfilled and resulted in a new resource being created.
Nested Schema : hubCertificate
Type:
Show Source
object-
fingerprintSHA1: string
Read Only:
trueThe certificate SHA-1 fingerprint. -
fingerprintSHA256: string
Read Only:
trueThe certificate SHA-256 fingerprint. -
issuer: string
Read Only:
trueThe distinguished name of the certificate issuer. -
keys: array
keys
Read Only:
true -
kid: string
Read Only:
trueThe key id -
lastUpdated: string
(date-time)
This indicates the last updated time of the certificate
-
status: boolean
The hub key status indicator
-
subject: string
Read Only:
trueThe distinguished name of the certificate subject. -
validFrom: string
(date-time)
Read Only:
trueThe date and time this certificate is valid from. -
validTo: string
(date-time)
Read Only:
trueThe date and time this certificate is valid to.
Nested Schema : hubCertificateKey
Type:
Show Source
object-
e: string
key public exponent
-
kid: string
key unique id
-
kty: string
key type
-
n: string
key modulus
-
use: string
key use
-
x5c: array
x5c
certificate of the key
400 Response
The request could not be processed because it contains missing or invalid information.
409 Response
The request could not be completed due to a conflict with the current state of the resource.