RA Profile
What is RA Profile?
RA Profile is a representation of attributes that collectively provides a complete configuration of the certificate service which can be used by users and applications in a consistent and convenient way.
RA Profile provides an abstraction of the certificate management service configuration attributes:
- Certification Authority and its related information
- Certificate management technology-specific attributes
- Service-related configuration
- Access control configuration
Additionally, RA Profile uses the following attributes to identify the service:
RA ProfileName- Description
Characteristics
Characteristics of RA Profile are:
- Binds the
Authorityand act as a specific certificate management service - Configures the certificate specific attributes and defines the compliance rules and behavior
- Provide rules for issuing, renewing, and revocation of the certificate
Process Flow
The following steps illustrate the process of requesting the certificate through the RA Profile:
Clientrequests theRA Profileto issue certificate providing the certificate signing requestRA Profilevalidates the certificate signing request against its configurationRA Profileforwards the certificate signing request and related attributes to theAuthority ProviderAuthority Providervalidates the certificate signing request and issues the certificateRA Profileforwards the certificate to theClient
Certificate Validation Settings
RA Profile can override platform certificate validation settings for certificates that are assigned to it. The following attributes are used to configure the certificate validation for the RA Profile:
| Name | Description | Default Value |
|---|---|---|
| Platform Validation Settings Used | If enabled, platform settings will be used for validation of certificates associated with the RA Profile, otherwise RA Profile settings will be used for validation | enabled |
| Validation Enabled | Enable or disable validation of certificates associated with the RA Profile | disabled |
| Validation Frequency | Validation frequency of certificates associated with the RA Profile specified in days | Everyday |
| Expiring Threshold | How many days before expiration should validation status of certificates associated with the RA Profile change to Expiring | 30 days |
Request attributes
RA Profile defines the request attributes of its certificate service — what the requester fills in on the request form and where each value lands in the issued certificate. If you are new to request attributes, read the Request Attribute concept first.
Each RA Profile can author its own static set of request attributes — see Configure request attributes for the authoring walkthrough.
The set the profile actually uses is the resolved set. The profile's merge mode decides how its static set combines with the request attributes its authority connector declares (Static only, Connector only or Merge), and the platform default set applies when the result is empty. See Where request-attribute sets come from.
External CSR validation
When a client supplies its own CSR (an external CSR), the RA Profile validates it against the resolved request-attribute set. Two modes exist:
- Strict — non-compliant external CSRs are rejected.
- Lenient — non-compliant external CSRs are accepted; violations become warnings. The certificate is issued. The warnings are informational: they are returned as
requestAttributeWarningsin the response of the REST issuance operations and shown on the issue form. See Warnings under lenient validation.
Validation checks:
- every mapped field of a required attribute has a matching subject component, SAN entry, or extension in the CSR
- matched values satisfy the attribute's value constraints
- in strict mode additionally a whitelist pass: anything present in the CSR — a subject component, SAN type, Key Usage, Extended Key Usage, or extension — that is not covered by the resolved set is a violation
The whitelist runs against the resolved request-attribute set. With no authored set, the platform default applies — six subject (RDN) attributes that map no SAN types and no extensions — so Strict rejects any CSR carrying a SAN entry or an extension. In particular, ACME enrollment always fails, because ACME CSRs carry a dNSName SAN. Enable strict mode only on profiles whose authored set covers the SAN types and extensions your clients send; otherwise use Lenient.
Key Usage and Extended Key Usage are admitted by mapping an attribute to their own typed targets; a new generic extension mapping for them is not accepted, while definitions saved earlier with one keep working. Other extensions that clients commonly place in a CSR, such as Basic Constraints, are built in to the OID registry, so admitting them is a matter of mapping an attribute to them; no Custom OID entry is needed. Vendor-specific extensions, such as the Microsoft certificate-template OIDs sent by Windows autoenrolment, must be registered first.
The mode is inherited along a chain: the profile's own setting, then the platform default, then lenient as the final fallback.
Configuration is per profile, in the web interface or API — see Configure external CSR validation.
Warnings under lenient validation
A warning is raised only for a CSR supplied by the client. A request the platform builds from a platform key never raises one. When the platform cannot check the request, because the connector's request attributes are unavailable, the request is accepted with a warning saying that the validation could not be performed.
The warnings are returned as requestAttributeWarnings in the response of the issue, issue-existing, renew and rekey operations. The field is also present in the response of the register operation but is always empty: registration is checked when the registered certificate is completed. The certificate is issued whether or not there are warnings.
Requests that arrive through ACME, SCEP and CMP are validated the same way, but nobody reads the warnings: they are written to the log. A violation under strict validation is returned as the error of the protocol.