Optimizing Certificate Issuance

When an application needs a certificate, the requester needs to know which policy applies, where the key pair will come from and whether approval is required. The MTG CLM issuance wizard brings these choices into one request that you can track through issuance.


Challenge

When teams request certificates through several tools, they may prepare certificate signing requests (CSRs) on the command line, switch between certificate authority (CA) interfaces and handle generated private keys separately. Those handoffs make it harder to check request details, track approvals and account for copies of private keys.

Solution Integration

In MTG CLM, requesters select a realm, certificate policy and end entity before submitting a request. The selected policy determines the certificate provider, allowed parameters and any approval requirements that apply to the request.

The Four-Step Issuance Workflow

Use the certificate issuance wizard to set the scope, policy, identity and key source for a request.

  1. Select the Operational Realm Select the realm that will contain the certificate. Access depends on the permissions assigned to each user or API client, which may cover more than one realm.

  2. Apply the Certificate Policy Select a configured policy for the request. Review its certificate provider, allowed certificate parameters and approval settings.

  3. Bind the End Entity Select the end entity for the certificate. Review its subject details and any DNS names or IP addresses needed for the request.

  4. Define the Certificate Source

    Choose a key pair mode allowed by the selected policy. Two examples are:

    • PKCS#10 Request: Upload a certificate signing request (CSR) for a key pair generated outside MTG CLM.

    • Server-Side Generation: MTG CLM generates the key pair. The policy’s Persist Private Key setting controls whether the private key is retained after download.

    Specify Cryptographic Parameters

    For Server-Side Generation:

    • Algorithm: Choose an algorithm allowed by the policy.

    • Key Parameters: Select an allowed key size or curve for the chosen algorithm.

    • Validity Period: Review the requested certificate lifetime. The CA configuration may affect the final validity period.

Request Processing and Approval

After completing the wizard, review the certificate request status. The policy determines which steps apply:

  • A request can proceed without manual review when the policy allows it.

  • If E-mail Verification Required is enabled and the end entity has an email address, the request waits for email verification.

  • If a request requires manual approval, an authorized user reviews it. If Dual Control is also enabled, two different authorized users must approve it. Check Approval Validity to see whether a previous approval can be reused.

Benefits

Requesters can review the identity, policy and key source together and track the status of the submitted request. The same information helps operators check the issued certificate before deployment.

Configuration Checks

Configuration Goal MTG CLM Control What to Verify

Access to certificate resources

Realm and permissions

Check the assigned realm and any global permissions for the accounts that request or manage certificates.

Intended certificate identity

Policy, end entity and certificate request

Verify the identity details for the request and compare the issued certificate with the intended subject and SANs.

Key generation and storage

Allowed key pair modes and cryptographic parameters

Check the key pair mode, algorithm and applicable key size or curve. For server-generated keys, review the private key retention setting.

Request review

Policy approval settings

Check whether the request requires manual review or qualifies for a previous approval.

Use Cases

Request a server certificate using an existing key pair

Choose a TLS policy that allows PKCS#10 requests. Select the end entity for the service, confirm the required DNS names and upload the CSR for the existing key pair. After issuance, verify the certificate’s subject and SANs before deploying it.

Request a certificate with a server-generated key

Select a policy that allows server-side generation, then choose an allowed algorithm and key size or curve. Check the request status for any required approval. Once the certificate is issued, download the key as permitted by the policy and securely transfer it to the system that needs it.

Troubleshooting

Policy Mismatch

Verify end entity attributes comply with policy requirements.

Validation Failures

Check that user information matches identity provider data.

CA Connection Issues

Ensure selected CA is operational and accessible.

Request Declined

Review policy requirements and resubmit with correct information.