Register Certificate
Pre-registration splits certificate issuance in two. You register the certificate's identity now and issue it later. No key or CSR exists yet.
This is different from issuing a certificate. Issuance needs a CSR or a platform key up front. Pre-registration needs neither — only the identity, described by the request attributes of the selected RA Profile, and, optionally, a challenge secret to gate the later completion.
Registration variants
Pre-registration comes in two variants:
- Connector-backed — the
Authority's connector supports registration. The identity is pre-registered at the upstream CA. - Platform-level — the connector does not support registration, or the authority has no connector. The certificate is pre-registered inside the platform only, with no CA call. It does not imply a CA-side end-entity exists.
You do not choose the variant. The platform picks it based on the capabilities of the Authority's connector.
Register a certificate using the web interface
- Click Certificates in the left menu
- Click Add Certificate (plus symbol )
- Select the request type Pre-register — register a certificate to be issued later using a challenge secret
- Select the
RA Profile - Fill the Request Attributes tab — these values are the identity of the future certificate
- Optionally enter a Challenge — an authorization secret that gates completion. If set, it must be 12–255 printable ASCII characters; you choose it, and the platform never generates one. Leave it blank to pre-register without a completion secret.
- Set the Issuance window (optional) — the deadline for completing the registration. When omitted, the platform default applies.
- Fill the Custom Attributes tab as usual
- Click Create
Registration states
Where the certificate lands depends on the variant. A platform-level registration, or a connector that registers synchronously, reaches Registered immediately. A connector that accepts the registration asynchronously leaves the certificate in Pending Registration until the platform confirms completion, after which it becomes Registered. See Certificate for the full state model.
When a challenge was set, the registration carries an authorization state — a challenge-less registration has none — shown in the Registration widget of the certificate detail. The widget shows the rows State, Expires, and Failed attempts. The state is one of:
Active— the challenge gates issue, renew and rekey.Expired— the issuance window has passed.Locked— locked after too many failed challenge attempts.Closed— behaves as unregistered.
Complete the registration
- Click Certificates in the left menu and open the
Registeredcertificate - Click Complete (check symbol ). The action is enabled only while the registration is
Activeand the issuance window has not elapsed; otherwise the disabled button's tooltip explains why. - In the Complete Certificate Registration dialog, enter the Challenge if the registration set one
- Upload the CSR — a certificate signing request for the key pair that will back the certificate. Completing a registration always requires a CSR; issuing from a platform key is not supported for registered certificates.
- Click Complete
The identity from the registration is preserved. Completion runs through the standard issue flow.
A registration with a challenge can also be completed by a SCEP or CMP client, through a profile whose challenge source is Certificate Registration; see Challenge source.
Register a successor
You can pre-register the certificate that will replace an issued or revoked one. The successor is a certificate in the Registered state that is completed later, and it is shown on the Related Certificates of the source as a Pending successor. How the relation resolves once the successor is issued is described in Relation Type Determination.
In the web interface, the source must be an issued certificate:
- Click Certificates in the left menu and open the issued certificate
- Click Renew and switch on Register instead of renewing now, or click Rekey and switch on Register instead of rekeying now. The dialog shows the identity of the source read-only: its request attributes, or its subject DN and SANs when it has none
- Enter the Challenge of the successor. It is required when the registration of the source is
Active. Optionally set the Issuance window, which is possible only together with a challenge - Fill the Connector Attributes that the connector asks for when registering. The custom attributes of the source are carried over
- Click Register. It stays disabled while the identity of the source cannot be carried over exactly (the dialog names the SAN types that cause it) and until the connector's register attributes are loaded
Complete the successor later with Complete, as for any registered certificate.
With the API, add the sourceCertificateUuid of the source to the register request. The source can be issued or revoked; a revoked certificate can be the source only through the API.
Register a certificate using the API
Pre-register a certificate using the Client Operations API. Provide the identity via csrAttributes OR the flat subjectDn/subjectAltName/extensions fields — never both. The challenge is optional: add authorizationSecret to gate completion, and — only alongside a challenge — the completion deadline as expiresAt (the platform rejects expiresAt without a challenge). A registration created without a challenge has no authorization gating and no issuance window.
curl -X POST \
--cacert [ca-cert] \
--cert [client-cert] \
--cert-type [type] \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
--data '
{
"csrAttributes": [
{
"uuid": "9abaeba0-973d-11ed-a8fc-0242ac120002",
"name": "commonName",
"version": "v3",
"contentType": "string",
"content": [
{
"contentType": "string",
"data": "server01.example.com"
}
]
}
],
"authorizationSecret": "correct-horse-battery-staple"
}' \
https://[domain]:[port]/api/v2/operations/authorities/e045a12a-e114-45ed-90b8-bac7e750e803/raProfiles/166b5cf5-63f2-11ec-90d6-0242ac120003/certificates/register
#https://[domain]:[port]/api/v2/operations/authorities/{authorityUuid}/raProfiles/{raProfileUuid}/certificates/register
Each csrAttributes entry is a request attribute of the RA Profile, with its value in data. Take its uuid, name and contentType from Get CSR Generation Attributes called with the profile's raProfileUuid; the example uses commonName from the platform default set.
The response carries the pre-registered certificate's uuid:
{
"uuid": "9c1f0a7e-52d3-4b1a-8f6e-2d7c30a41b95"
}
To complete the registration, call the issue operation on the pre-registered certificate:
POST /api/v2/operations/authorities/{authorityUuid}/raProfiles/{raProfileUuid}/certificates/{certificateUuid}/issue
The body carries the CSR (request) and, when the registration set a challenge, the authorizationSecret. A CSR is required — the platform-key selection (tokenProfileUuid/keyUuid) is not supported when completing a registered certificate.
Platform defaults
Two platform settings provide the registration defaults. You edit them in platform settings, on the Certificates tab in the Registration section:
- Default Issuance Window (days) — applied when a pre-registration omits an explicit expiry.
- Max Failed Attempts — maximum failed challenge-verification attempts before the registration authorization locks.