Skip to main content

Create a certificate template

A certificate template defines the structure and constraints of certificates issued through a certificate management policy. It specifies settings such as key types, signature algorithms, subject information, certificate extensions, and other certificate fields.

Device Trust Manager supports the following template formats:

  • X.509: The International Telecommunication Union (ITU) standard format of public key certificates. It supports RSA and ECDSA certificates

  • Global platform: These certificates are around one-tenth the size of an X.509 certificate. It supports ECDSA certificates only

  • Attribute certificate: An RFC 5755 certificate that assigns authorization attributes to an existing holder; it does not bind a new public key

Dica

  • During onboarding, DigiCert​​®​​ provides commonly used certificate templates, such as client authentication certificate template and basic TLS certificate template, so you can begin issuing certificates immediately. In many cases, these predefined templates satisfy common deployment requirements and do not require further customization.

  • If your organization requires custom certificate settings, you can create and manage your own certificate templates. To do so, see the Certificate template structure, which provides detailed guidance for creating and customizing X.509, GlobalPlatform, and Attribute Certificate templates, including supported properties, JSON structures, and configuration examples.

Before you begin

Before creating certificate templates, ensure:

  • You have a user role that contains the Solution administrator permission

  • You know which Issuing CA will issue certificates from the certificate profiles based on this template

  • You know the intended certificate purpose, such as client authentication or server authentication

  • You know which key types and signature algorithms the issuer and devices support

  • You know which Subject and SAN values will come from a CSR; a fixed profile value or a request

  • You have identified the accounts that should be allowed to use this template

  • You know the certificate template structure and JSON, and need exact property-level control

  • You have a valid JSON certificate template that follows the supported certificate template schema

To create a certificate template:

  1. In the Device Trust Manager menu, go to Certificate management > Certificate settings.

  2. Select Create a certificate template.

  3. Provide a Template name.

    The template name appears when selecting a certificate template, while creating certificate profiles, and certificate management policies.

  4. Select the Certificate template type and Format from the available options:

    • End entity: Used for certificates issued to devices, users, servers, applications, and other non-CA entities

      Device Trust Manager supports the following template formats for end-entity certificate template:

    • Intermediate CA: A subordinate certification authority, authorized by a root or another CA to issue certificates. Intermediate CAs are used as your Device Trust Manager Issuing CA.

      Device Trust Manager supports only X.509 template format for Intermediate CA

    Dica

    Certificate template type guidance

    Certificate templates for Intermediate CA certificates are largely the same as End entity certificate templates. In most cases, you can configure the same certificate attributes, extensions, and issuance settings. However, the following settings behave differently depending on the certificate template type:

    End entity certificate templates: When you create an End entity certificate template:

    • The CA flag in the basic_constraint extension should not be enabled

    • The path length setting is ignored because it applies only to CA certificates

    Intermediate CA certificate templates: When you create an Intermediate CA certificate template:

    • If the template includes basic_constraint extension, set the CA flag to true

    • Don't configure the Key Usage extension in the template. The CA automatically applies the appropriate key usage values when issuing intermediate CA certificates. Any key usage values defined in the template are rejected

    • The path length setting controls how many subordinate CA levels can exist beneath the intermediate CA:

      • A value of 0 allows the intermediate CA to issue only end-entity certificates

      • A value greater than 0 specifies the maximum number of subordinate CA levels that can be created

      • A value of -1 excludes the path length constraint from the certificate

  5. In the Template body, paste or enter the JSON definition for the certificate template.

    JSON structure example:

    The following example shows a JSON structure of a certificate template:

    {
      "key_gen": {
        "enabled": true,
        "key_type": {
          "allowed_types": [
            "ecdsa"
          ],
          "default_key_type": "ecdsa"
        },
        "ecdsa_curve": {
          "allowed_curves": [
            "P-256",
            "P-384",
            "P-521"
          ],
          "default_curve": "P-256"
        }
      },
      "issue_types": [
        "client_authentication"
      ],
      "signature_algorithm": {
        "allowed_algorithms": [
          "sha256WithECDSA",
          "sha384WithECDSA",
          "sha512WithECDSA",
          "match_issuer"
        ],
        "default_algorithm": "match_issuer"
      },
      "subject": {
        "attributes": [
          {
            "type": "common_name",
            "include": "optional",
            "encoding": "auto",
            "allowed_source": [
              "csr",
              "fixed_value",
              "user_supplied"
            ]
          }
        ]
      },
      "extensions": {
        "key_usage": {
          "critical": true,
          "required_usages": {
            "rsa": [
              "digital_signature",
              "key_encipherment"
            ],
            "ecdsa": [
              "digital_signature"
            ]
          },
          "optional_usages": {
            "rsa": [
              "data_encipherment"
            ],
            "ecdsa": [
              "key_agreement"
            ]
          }
        },
        "extended_key_usage": {
          "critical": true,
          "include": "optional",
          "required_usages": [
            {
              "oid": "client_authentication",
              "name": "Client Authentication"
            }
          ]
        }
      },
      "serial_number_size": 20,
      "validity": {
        "min_duration": {
          "value": 1,
          "unit": "DAYS"
        },
        "max_duration": {
          "value": 10,
          "unit": "YEARS"
        },
        "default_duration": {
          "value": 10,
          "unit": "YEARS"
        }
      }
    }
  6. Under Limited accounts, select the accounts that can use this template.

  7. When ready, select:

    • Create: The completed certificate template will now appear on the Certificate templates page and forms where template data is required

    • Create and select: Create the certificate template and continue to Certificate profile creation section

The certificate template is now available on the Certificate templates page and can be used when creating certificate profiles and certificate management policies.