Skip to main content

CMP Profile

CMP Profile specifies the configurations of the CMP server behaviour. It holds the configuration listed below:

ConfigurationPurposeDefault ValueMandatory
NameCMP Profile NameYes
DescriptionDescription of the CMP ProfileNo
Challenge SourceHow requests are authenticated: with the protection configured on the profile, or with the challenge of a certificate registration. See Challenge sourceProtocol DefaultNo
VariantVariant of the CMP protocol defining the behaviourYes
Request Protection MethodOne of available protection methods for the CMP requestsYes
Shared SecretShared secret for the protection of CMP message when request protection method is shared secretNo
Response Protection MethodOne of available protection methods for the CMP responsesYes
Signing CertificateCertificate used for signing CMP responses whn the response protection method is signatureYes

Supported CMP variants​

The platform supports the following CMP variants:

info

The CMP variant CMPv3 is prepared for future use case according to the RFC 9483 - Lightweight Certificate Management Protocol (CMP) Profile, however, not yet fully implemented.

Request and response protection methods​

The platform supports the following protection methods for CMP requests and responses:

The following restrictions apply for the protection methods configuration:

  • If the Response Protection Method is set to Shared Secret, the Shared Secret protection method must be configured also for the Request Protection Method
  • If the Request Protection Method is set to Signature, the Signature protection method must be used also for the Response Protection Method

Challenge source​

With the challenge source Protocol Default, requests are authenticated by the Request Protection Method of the profile: with its Shared Secret, or by a signature.

With Certificate Registration, a request names a registered certificate by its UUID in the senderKID, and the challenge of that registration is the shared secret of the message protection. Initialization (ir), certification (cr) and key update (kur) requests, and their pollReq and certConf messages, are authenticated this way. Once the protection is verified, the subject and SANs of the request must equal the registered identity. See Challenge source for how a failed request is refused.

The following restrictions apply to a profile with the challenge source Certificate Registration:

  • The variant must be CMPv2
  • The Request Protection Method must be Shared Secret, and no shared secret is configured on the profile
  • The Response Protection Method can be either Shared Secret or Signature
  • Revocation requests (rr) are refused
  • The senderKID of a key update must be the UUID of the certificate being updated. After a successful key update the registration follows the new certificate, so the next key update names the UUID of the new certificate

Request signing certificate​

When the Request Protection Method is set to Signature, the request must contain signing certificate in the PKIMessage extraCerts field. The first certificate in the extraCerts field is used for the signature verification.

Response signing certificate requirements​

The certificate with associated private key should be available in the inventory in case Response Protection Method is set to Signature. The certificate should meet the following criteria:

  • The certificate should be valid
  • The certificate should have associated private key managed by the platform
  • The private key should be valid and active
  • The private key should have the Key Usage set to Sign

Operations on CMP Profile​

The following operations can be performed on the CMP Profile:

OperationDescription
CreateCreate a new CMP Profile. New CMP Profile is disabled by default
UpdateUpdate configuration of already existing CMP Profile
DeleteDelete existing CMP Profile
DisableDisable existing CMP Profile. All request to disabled CMP Profile will be rejected
EnableEnable existing CMP Profile