Skip to main content

Certificates

Sign certificates and check certificate status.

📄️Sign a custom certificate signing request

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.

📄️Process an OCSP request

Checks the revocation status of the certificates in a DER-encoded OCSP request and returns a signed OCSP response. Requires the OCSP responder to be enabled (the combine.tap.certificates.ocsp Configuration Value, default false). Does not require a client certificate or the X-Requested-By header, and is also served over HTTP. A request larger than the combine.tap.ocsp.responder.request.byteLimit Configuration Value (default 8,192 bytes) receives an OCSP malformedRequest response, even when the responder is not enabled. A certificate not issued by the deployment's signer certificate authority is reported as unknown. The response is signed with the signer certificate authority's key, echoes the request's nonce, and sets nextUpdate to the combine.tap.ocsp.responder.nextUpdate.duration Configuration Value (default 86,400,000 milliseconds) after the time of the response.

📄️Process an OCSP request (GET)

The RFC 6960 GET form of the OCSP responder. Checks the revocation status of the certificates in the OCSP request carried in the rest of the path and returns a signed OCSP response. Requires the OCSP responder to be enabled (the combine.tap.certificates.ocsp Configuration Value, default false). Does not require a client certificate, and is also served over HTTP. A request that is not valid Base64 receives an OCSP malformedRequest response, even when the responder is not enabled. Over HTTPS, a path that contains an encoded slash (%2F) is rejected with 400 before it reaches the responder; over HTTP, as in the OCSP responder URL of an issued certificate, it is accepted.