Sign a custom certificate signing request
POST/tap/api/v1/admin/certificate/custom
Signs a PEM-encoded PKCS#10 certificate signing request and returns the signed certificate. Requires the admin role. Requires custom CSR signing to be enabled (the combine.tap.api.certificates.signCustomCSR.enable Configuration Value, default false). A caller without the admin role, or a deployment where custom CSR signing is not enabled, receives 500 with the Combine HTML error page. The CSR's signature is not verified. Only an RSA public key can be signed, and a CSR that omits its attributes field cannot be signed; both return 500. The certificate is issued by the deployment's signer certificate authority and is valid for two years. It has the CSR's subject and public key, the DNS names from the CSR's subject alternative name extension, client and server authentication extended key usage, and an OCSP responder URL when the OCSP responder is enabled. Its serial number is a random number from 1,000,000 to 1,999,999, which never identifies a TAP user account, so the certificate cannot be used to call the TAP API.
Request
Responses
- 200
- 400
- 413
- 500
The signed certificate in PEM format.
The request body has no PEM object, or its first PEM object is not a certificate signing request.
The request body is longer than the combine.tap.api.certificates.signCustomCSR.byteLimit Configuration Value (default 65,536 characters).
The certificate signing request could not be signed (plain text), including a PEM object that cannot be parsed, a public key that is not RSA, and a CSR that omits its attributes field; or the caller does not have the admin role or custom CSR signing is not enabled (the Combine HTML error page).