Skip to content

Latest commit

 

History

History
32 lines (30 loc) · 4.58 KB

certificate-profile-OCSP-responder.md

File metadata and controls

32 lines (30 loc) · 4.58 KB

Delegated OCSP Responder Certificate Profile

Field Value
Version V3 (2)
Serial Number Must be a unique positive integer with a minimum of 64 bits
Issuer Signature Algorithm sha256 WithRSAEncryption {1 2 840 113549 1 1 11}
Issuer Distinguished Name Distinguished Name of the OCSP Responder Certificate CA Issuer
Validity Period Expressed in UTC Time for dates until end of 2049 and Generalized Time for dates thereafter
No longer than 45 days from date of issue.
Goal of certificates is issued every 30 days with a 15 day grace period. Renewed certificates 30 days longer than previous certificate.
Rekey <= every 3 years.
Subject Distinguished Name Unique X.500 CA DN as specified in Section 7.1.4 of this CP

Geo-political SDNs:
CN indicates OCSP Responder
Organization Name = U.S. Government
Organization Unit (optional)
Country (required) two-letter ISO 3166-1 country code - US

Domain Component Names:
If present, TLD must be .mil or .gov and name must contain second level domain IAW registry.
(each X.500 DN each RDN is a printableString where possible and contains a single attribute type and attribute value tuple. RDN of type DC are encoded as IA5string. )
Subject Public Key Information Public key algorithm associated with the public key.
May be either RSA or elliptic curve.
RSA Encryption {1.2.840.113549.1.1.1}
Elliptic curve key {1.2.840.10045.2.1}
Parameters:
For RSA, parameters field is populated with NULL.
For ECC Implicitly specify parameters through an OID associated with a NIST approved curve referenced in 800-78-1:
Curve P-256 {1.2.840.10045.3.1.7}
Curve P-384 {1.3.132.0.34}
Curve P-521 {1.3.132.0.35}

For RSA public keys, modulus must be 2048, 3072, or 4096 bits, an odd integer, not the power of a prime, with no factors < 752. Public exponent must be an odd integer ≥ 3 (recommended that it be between 216+1 and 2256-1.) (Source: Appendix A, CA/Browser Forum, Baseline Requirements)
For ECC, public key must be at least 224 bits.
Issuer Signature sha256 WithRSAEncryption {1 2 840 113549 1 1 11}
Extension Required Critical Value
Authority Key Identifier Mandatory False Octet String: Derived using the SHA-1 hash of the Issuer’s public key. Must match SKI of issuing CA Certificate
basicConstraints Optional True If present:
cA=False
Subject Key Identifier Mandatory False Octet String
20 byte SHA-1 hash of the binary DER encoding of the OCSP Responder public Key
Key Usage Mandatory True Required Key Usage:
Digital Signature

Prohibited Key Usage:
All others
id-pkix-ocsp-nocheck {1.3.6.1.5.5.7.48.1.5} Mandatory False Null
Extended Key Usage False Required Extended Key Usage:
id-kp-OCSPSigning {1.3.6.1.5.5.7.3.9}
Prohibited Extended Key Usage:
All others, including anyEKU EKU {2.5.29.37.0}
Certificate Policies Mandatory False Required Certificate Policy Fields:
At least one certificate policy OID defined or listed in Section 1.2 of the CP

Optional Certificate Policy Fields:
certificatePolicies:policyQualifiers
policyQualifierId id-qt 1
qualifier:cPSuri
Subject Alternative Name Optional False
Authority Information Access Mandatory False Required AIA Fields

** Id-ad-caIssuers**
Publicly accessible URI of Issuing CA’s certificate accessMethod = {1.3.6.1.5.5.7.48.2}
Shall include at least 1 instance of an HTTP URL containing the Issuing CA’s certificate
CRL Distribution Points Optional False At least one HTTP URI to the location of a publicly accessible CRL. The reasons and cRLIssuer fields must be omitted.
IssuerAltName Not Used
Subject Directory Attributes Not Used
Private Extensions Not Used False
Private Key Usage Period Optional False
nameConstraints Not Used
Policy Mapping Not Used
Policy Constraints Not Used