Certificates

Crescendo Manager allows you to generate new public-private key pairs with your tokens.

To generate a new key pair with the selected token:

1. Go to the Certificates view in the left navigation pane.

2. Click the Generate link on the desired slot.

   

3. The Generate Key, CSR or Certificate dialog opens, with the New key generation action and the specific slot already pre-selected.

   

   (An alternative to the Generate link is to click the Generate button in the top-right corner of the Certificates view and select New key from the Select action drop-down.)

   

4. Key Type: Select the key pair type to generate. The key pair type determines the cryptographic algorithm and key length.

   Available options:

   • RSA 2048 (default): 2048-bit Rivest-Shamir-Adleman key

   • RSA 3072: 3072-bit Rivest-Shamir-Adleman key

   • RSA 4096: 4096-bit Rivest-Shamir-Adleman key

   • ECC P-256: Elliptic curve-based 256-bit key.

   • ECC P-384: Elliptic curve-based 384-bit key.

5. Choose Key Slot: If necessary, you can select a different slot for generating the new key pair.

   Available options:

   • First available slot: The key will be generated in the first free slot. You can select this option if the key usage is not important.

   • Authentication (9A)

   • Signature (9C)

   • Key Management (9D)

   • Card Authentication (9E)

   • First available History Slot

   • SKI Transport Key RSA-3072 key uniquely bound to a specific token, used to securely transfer data to that token in compliance with the Secure Key Injection protocol.: Select this option to generate an RSA-3072 key for encrypting keys for Secure Key Injection. The Key Type field will be set to RSA 3072 automatically.

   • First General-Purpose Slot

6. Key Name: The key name is a human-readable string used to identify the key. Use the randomly generated value or overwrite it.

   Note:

   Knowing the key name is useful when you need to use the key directly, such as with the Cryptography Next Generation (CNG Cryptography Next Generation. A modern cryptographic API (Application Programming Interface) introduced by Microsoft as part of Windows to replace the older CryptoAPI. It provides a flexible and extensible framework for implementing cryptographic algorithms, key storage, and secure key management and supports a wide range of cryptographic operations, including encryption, decryption, hashing, and digital signatures.) application programming interface. See the simple PowerShell example below, which opens the key for further actions.

   Copy

   [System.Security.Cryptography.CngKey]::Open($keyname, [System.Security.Cryptography.CngProvider]::MicrosoftSmartCardKeyStorageProvider)

7. Click the Generate button. The new key is now displayed in the respective slot tile.

8. To copy the public key, click the tile. The private key cannot be accessed or retrieved.

Actions Available With an Existing Key

Once you have a key stored on your token, you can:

• Generate certificate signing requests for your key.

• Generate self-signed certificates for your key.

Crescendo Manager allows you to generate cryptographic keys and corresponding certificate signing requests (CSR) with your tokens.

To generate a new key and CSR with the selected token:

1. Go to the Certificates view in the left navigation pane.

2. Click the Generate button in the top-right corner of the Certificates view.

   

3. The Generate Key, CSR or Certificate dialog opens, with the New Key & generate CSR generation action and the First available slot pre-selected.

   

4. Key Type: Select the key pair type to generate. The key pair type determines the cryptographic algorithm and key length.

   Available options:

   • RSA 2048 (default): 2048-bit Rivest-Shamir-Adleman key

   • RSA 3072: 3072-bit Rivest-Shamir-Adleman key

   • RSA 4096: 4096-bit Rivest-Shamir-Adleman key

   • ECC P-256: Elliptic curve-based 256-bit key.

   • ECC P-384: Elliptic curve-based 384-bit key.

5. Choose Key Slot: The First available slot option is pre-selected. You can choose a different slot for generating the new key pair and CSR.

   Available options:

   • First available slot: The key and the CSR will be generated in the first free slot. Select this option if the key usage is not important.

   • Authentication (9A)

   • Signature (9C)

   • Key Management (9D)

   • Card Authentication (9E)

   • First available History Slot

   • First General-Purpose Slot

6. Key Name: The key name is a human-readable string used to identify the key. Use the randomly generated value or overwrite it.

   Note:

   Knowing the key name is useful when you need to use the key directly, such as with the Cryptography Next Generation (CNG Cryptography Next Generation. A modern cryptographic API (Application Programming Interface) introduced by Microsoft as part of Windows to replace the older CryptoAPI. It provides a flexible and extensible framework for implementing cryptographic algorithms, key storage, and secure key management and supports a wide range of cryptographic operations, including encryption, decryption, hashing, and digital signatures.) application programming interface. See the simple PowerShell example below, which opens the key for further actions.

   Copy

   [System.Security.Cryptography.CngKey]::Open($keyname, [System.Security.Cryptography.CngProvider]::MicrosoftSmartCardKeyStorageProvider)

7. Hash Algorithm: Select the hash algorithm used to create a digital representation (hash) of the data within the CSR. This hash is used to create a digital signature that proves the integrity and authenticity of the CSR.

   Available options:

   • SHA1

   • SHA256 (default)

   • SHA384

   • SHA512

   We recommend using SHA-256 (default) or higher.

8. Padding Scheme: If a RSA key type is selected, you can choose the padding A method used to add extra data to a hash before creating a digital signature with an RSA key to ensure that the resulting signature is unique and resistant to certain types of cryptographic attacks. scheme.

   • PKCS1 (Public Key Cryptography Standards #1)

   • PSS (Probabilistic Signature Scheme): PSS adds randomness to the padding process, making the signature more secure against certain types of cryptographic attacks.

     Important: PSS is considered more secure, but PSS-signed certificates may not be supported by older systems.

9. Subject (Distinguished Name): Add at least one Subject Distinguished Name component for your CSR.

   • Common Name is selected as default, but you can delete the value by clicking the Clear icon and select another option from the drop-down list.

   • Alternatively, you can type the attribute's long or short name or OID directly into the field.

   • Click the Add Value button to include additional attributes of your Subject Distinguished Name in the CSR.

10. Other x509 v3 Extensions (Advanced): If you need x509 v3 extensions to be added to your CSR:

    1. Click the Other x509 v3 Extensions (Advanced) drop-down button.

       

    2. The Subject Alternative Name (SAN) extension section will be displayed.

       

       (If you want to add a custom extension to your CSR, see point 11.)

    3. Click the toggle button to enable SAN in your CSR.

    4. A checkbox will appear to the left of the toggle button. If checked, the extension will be marked as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate..

       

    5. Click the Add SAN button for additional SAN entries. The number of SANs is not limited.

       The available types of SANs are:

       • IP Address

       • DNS Name

       • Email

       • URI (Unique Resource Identifier)

       • UPN (User Principal Name)

       Hover over the information icon to view example entries for each type.

11. To add custom extensions to your certificate, click the Add Custom Extension button in the Other x509 v3 Extensions (Advanced) field.

    • The Custom Extension section appears in the dialog.

      

    • The Name field for the custom extension is for informational purposes only.

    • Enter the custom extension object identifier (OID Object identifier. Globally unique identifiers standardized by the International Telecommunication Union. OIDs are represented as a series of numbers separated by dots (e.g., 2.5.29.37).) (e.g., 2.5.29.19).

    • Add the extension content in hexadecimal format.

    • To mark an extension as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate., check the checkbox to the left of the toggle button.

      

    • To remove an extension, click the trash bin icon .

12. Click the Generate button.

    The new key with the generated CSR is now displayed in the respective slot tile.

    

Crescendo Manager allows you to generate cryptographic keys and corresponding self-signed certificates with your tokens.

To generate a new key and self-signed certificate with the selected token:

1. Go to the Certificates view in the left navigation pane.

2. Click the Generate button in the top-right corner of the Certificates view.

   

3. The Generate Key, CSR or Certificate dialog opens, with the New Key & generate CSR action and the First available slot pre-selected.

   

4. Click the Select Action drop-down and select New key & generate self-signed certificate.

   

5. Key Type: Select the key pair type to generate. The key pair type determines the cryptographic algorithm and key length.

   Available options:

   • RSA 2048 (default): 2048-bit Rivest-Shamir-Adleman key

   • RSA 3072: 3072-bit Rivest-Shamir-Adleman key

   • RSA 4096: 4096-bit Rivest-Shamir-Adleman key

   • ECC P-256: Elliptic curve-based 256-bit key.

   • ECC P-384: Elliptic curve-based 384-bit key.

6. Choose Key Slot: The First available slot option is pre-selected. You can choose a different slot for generating the new key pair and self-signed certificate.

   Available options:

   • First available slot: The key and the self-signed certificate will be generated in the first free slot. Select this option if the specific type of key usage is not important.

   • Authentication (9A)

   • Signature (9C)

   • Key Management (9D)

   • Card Authentication (9E)

   • First available History Slot

   • First General-Purpose Slot

7. Key Name: The key name is a human-readable string used to identify the key. Use the randomly generated value or overwrite it.

   Note:

   Knowing the key name is useful when you need to use the key directly, such as with the Cryptography Next Generation (CNG Cryptography Next Generation. A modern cryptographic API (Application Programming Interface) introduced by Microsoft as part of Windows to replace the older CryptoAPI. It provides a flexible and extensible framework for implementing cryptographic algorithms, key storage, and secure key management and supports a wide range of cryptographic operations, including encryption, decryption, hashing, and digital signatures.) application programming interface. See the simple PowerShell example below, which opens the key for further actions.

   Copy

   [System.Security.Cryptography.CngKey]::Open($keyname, [System.Security.Cryptography.CngProvider]::MicrosoftSmartCardKeyStorageProvider)

8. Hash Algorithm: Select the hash algorithm used to create a digital representation (hash) of the data within the certificate. This hash is used to create a digital signature that proves the integrity and authenticity of the certificate.

   Available options:

   • SHA1

   • SHA256 (default)

   • SHA384

   • SHA512

   We recommend using SHA-256 (default) or higher.

9. Padding Scheme: If a RSA key type is selected, you can choose the padding A method used to add extra data to a hash before creating a digital signature with an RSA key to ensure that the resulting signature is unique and resistant to certain types of cryptographic attacks. scheme.

   • PKCS1 (Public Key Cryptography Standards #1)

   • PSS (Probabilistic Signature Scheme): PSS adds randomness to the padding process, making the signature more secure against certain types of cryptographic attacks.

     Important: PSS is considered more secure, but PSS-signed certificates may not be supported by older systems.

10. Basic Constraint (CA or End Certificate): Use this field to specify whether the certificate should be an end-entity certificate (default) or a Certificate Authority (CA) certificate.

    

    Available options:

    • End Entity: Issues a leaf certificate for an end user, server, or device.

    • Certificate Authority with max depth of 0: Issues a CA certificate that can only issue end-entity certificates (no CA certificates).

    • Certificate Authority with max depth of 1-4: Issues a CA certificate that can issue one to four levels of subordinate CA certificates, in addition to end-entity certificates.

    • Certificate Authority with unlimited depth: Issues a CA certificate that can issue an unlimited number of subordinate CA certificates. This setting is typically used for root CAs or higher-level CAs that need the capability to create multiple levels of CA certificates below them.

    Note: If you selected a CA certificate as the basic constraint, don't forget to specify appropriate key usage (see point 14).

11. Set the self-signed certificate validity: Use the Start Date field along with the validity period defined in days, or set the Expiration Date directly.

    

12. Serial Number: Enter a decimal or hexadecimal number for the certificate's serial number, or use the automatically generated value.

    

13. Subject (Distinguished Name): Specify at least one Subject Distinguished Name component for your self-signed certificate.

    • Common Name is selected as default, but you can delete the value by clicking the Clear icon and select another option from the drop-down list.

      

    • Alternatively, you can type the attribute's long or short name or OID directly into the field.

    • Click the Add Value button to include additional attributes of your Subject Distinguished Name in the self-signed certificate.

      

14. Key Usage: Use this section to specify the intended purpose of the certificate. The User Certificate template is pre-selected.

    

    You can select a template with pre-selected options, which you can edit, or choose the empty template to define the key usage from scratch.

    Click the drop-down button on the right to display key usage and extended key usage options.

    The available templates are:

    • Certificate Authority: You can use this template as a starting point if you selected a CA certificate as the basic constraint (see point 10.)

      

    • User Certificate(default)

      

    • Code Signing

      

    • OpenVPN Client

      

    • Empty

15. Other x509 v3 Extensions (Advanced): If you need x509 v3 extensions to be added to your certificate:

    1. Click the Other x509 v3 Extensions (Advanced) drop-down button.

       

    2. A list of most commonly used extensions will be displayed.

       

       If you want to add a custom extension to your certificate, see point 16.

    3. Click the toggle button to enable an extension in your certificate.

    4. A checkbox will appear to the left of the toggle button. If checked, the extension will be marked as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate..

       

       • Subject Alternative Name:

         • IP Address

         • DNS Name

         • Email

         • URI (Unique Resource Identifier)

         • UPN (User Principal Name)

         Hover over the information icon to view example entries for each type.

         Click the Add SAN button for additional SAN entries. The number of SANs is not limited.

       • CRL Distribution Points:

         Specify the HTTPS or LDAP endpoints' URLs where the Certificate Revocation List (CRL) can be accessed.

         Click the Add CRL button for additional CRL distribution point entries. The number of entries is not limited.

       • Subject Key Identifier

         This field is used to uniquely identify the certificate. Its value is typically the SHA-1 hash of the subject's public key.

         If not enabled, the correct value will be automatically filled in during generation. You may enter your own value for testing purposes.

       • Authority Information Access:

         This extension specifies the locations where information about the issuing Certificate Authority (CA) certificate can be found, typically HTTP or LDAP URIs.

         Select the access method to retrieve information about the CA certificate and enter the corresponding value:

         • OCSP: Specify the URI for the Online Certificate Status Protocol (OCSP) responder, which checks the revocation status of the certificate.

         • CA Issuer: Specify the URI for the issuing CA’s certificate.

    5. To remove an extension, click the trash bin icon .

16. To add custom extensions to your certificate, click the Add Custom Extension button in the Other x509 v3 Extensions (Advanced) field.

    1. The Custom Extension form will appear in the dialog:

       

    2. Enter a Name for the custom extension. This value is for informational purposes only.

    3. Enter the custom extension's object identifier (OID Object identifier. Globally unique identifiers standardized by the International Telecommunication Union. OIDs are represented as a series of numbers separated by dots (e.g., 2.5.29.37).) (e.g., 2.5.29.19).

    4. Add the extension's content in hexadecimal format.

    5. To mark an extension as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate., check the checkbox to the left of the toggle button.

       

    6. To remove an extension, click the trash bin icon .

17. Click the Generate button.

    The new key with the generated certificate is now displayed in the respective slot tile:

    

If you have a key stored on your token, you can generate corresponding certificate signing requests (CSRs) with it.

To generate a CSR using an existing key:

1. Go to the Certificates view in the left navigation pane.

2. Click the Generate CSR icon on the slot holding the existing key.

   

    

3. The Generate Key, CSR or Certificate dialog opens, with the Existing key & generate CSR generation action and the key stored in the respective slot pre-selected.

   

   Alternatively, you can click the Generate button in the top-right corner of the Certificates view.

   

   In the Generate dialog, select Existing Key & generate CSR from the Select action drop-down.

   

4. Choose Existing Key: Use this drop-down to select other than the pre-selected key to generate the CSR for.

5. Hash Algorithm: Select the hash algorithm used to create a digital representation (hash) of the data within the CSR. This hash is used to create a digital signature that proves the integrity and authenticity of the CSR.

   The available options are:

   • SHA1

   • SHA256 (default)

   • SHA384

   • SHA512

     We recommend using SHA-256 (default) or higher.

6. Padding Scheme: If a RSA key type is selected, you can choose the padding A method used to add extra data to a hash before creating a digital signature with an RSA key to ensure that the resulting signature is unique and resistant to certain types of cryptographic attacks. scheme.

   • PKCS1 (Public Key Cryptography Standards #1)

   • PSS (Probabilistic Signature Scheme): PSS adds randomness to the padding process, making the signature more secure against certain types of cryptographic attacks.

     Important: PSS is considered more secure, but PSS-signed certificates may not be supported by older systems.

7. Subject (Distinguished Name): Add at least one Subject Distinguished Name component for your CSR.

   • Common Name is selected as default, but you can delete the value by clicking the Clear icon and select another option from the drop-down list.

     

   • Alternatively, you can type the attribute's long or short name or OID directly into the field.

   • Click the Add Value button to include additional attributes of your Subject Distinguished Name in the CSR.

8. Other x509 v3 Extensions (Advanced): If you need x509 v3 extensions to be added to your CSR:

   1. Click the Other x509 v3 Extensions (Advanced) drop-down button.

      

   2. The Subject Alternative Name (SAN) extension section will be displayed.

      

      (If you want to add a custom extension to your CSR, see point 9.)

   3. Click the toggle button to enable SAN in your CSR.

   4. A checkbox will appear to the left of the toggle button. If checked, the extension will be marked as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate..

      

   5. Click the Add SAN button for additional SAN entries. The number of SANs is not limited.

      The available types of SANs are:

      • IP Address

      • DNS Name

      • Email

      • URI (Unique Resource Identifier)

      • UPN (User Principal Name)

      Hover over the information icon to view example entries for each type.

9. To add custom extensions to your certificate, click the Add Custom Extension button in the Other x509 v3 Extensions (Advanced) field.

   • The Custom Extension section appears in the dialog.

     

   • The Name field for the custom extension is for informational purposes only.

   • Enter the custom extension object identifier (OID Object identifier. Globally unique identifiers standardized by the International Telecommunication Union. OIDs are represented as a series of numbers separated by dots (e.g., 2.5.29.37).) (e.g., 2.5.29.19).

   • Add the extension content in hexadecimal format.

   • To mark an extension as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate., check the checkbox to the left of the toggle button.

   

   • To remove an extension, click the trash bin icon .

10. Click the Generate button.

    The generated CSR has been added to the key in the respective slot.

    

If you have a key stored on your token, you can generate corresponding self-signed certificates with it.

To generate a self-signed certificate using an existing key:

1. Go to the Certificates view in the left navigation pane.

2. Click the Generate button in the top-right corner of the Certificates view.

   

3. The Generate Key, CSR or Certificate dialog opens, with the New Key & generate CSR action and the First available slot pre-selected.

   

4. Click the Select Action drop-down and select Existing key & generate self-signed certificate and select an existing key.

   

5. Hash Algorithm: Select the hash algorithm used to create a digital representation (hash) of the data within the self-signed certificate. This hash is used to create a digital signature that proves the integrity and authenticity of the certificate.

   Available options:

   • SHA1

   • SHA256 (default)

   • SHA384

   • SHA512

   We recommend using SHA-256 (default) or higher.

6. Padding Scheme: If a RSA key type is selected, you can choose the padding A method used to add extra data to a hash before creating a digital signature with an RSA key to ensure that the resulting signature is unique and resistant to certain types of cryptographic attacks. scheme.

   • PKCS1 (Public Key Cryptography Standards #1)

   • PSS (Probabilistic Signature Scheme): PSS adds randomness to the padding process, making the signature more secure against certain types of cryptographic attacks.

     Important: PSS is considered more secure, but PSS-signed certificates may not be supported by older systems.

7. Basic Constraint (CA or End Certificate): Use this field to specify whether the certificate should be an end-entity certificate (default) or a Certificate Authority (CA) certificate.

   

   Available options:

   • End Entity: Issues a leaf certificate for an end user, server, or device.

   • Certificate Authority with max depth of 0: Issues a CA certificate that can only issue end-entity certificates (no CA certificates).

   • Certificate Authority with max depth of 1-4: Issues a CA certificate that can issue one to four levels of subordinate CA certificates, in addition to end-entity certificates.

   • Certificate Authority with unlimited depth: Issues a CA certificate that can issue an unlimited number of subordinate CA certificates. This setting is typically used for root CAs or higher-level CAs that need the capability to create multiple levels of CA certificates below them.

   Note: If you selected a CA certificate as the basic constraint, don't forget to specify appropriate key usage (see point 11).

8. Set the self-signed certificate validity: Use the Start Date field along with the validity period defined in days, or set the Expiration Date directly.

   

9. Serial Number: Enter a decimal or hexadecimal number for the certificate's serial number, or use the automatically generated value.

   

10. Subject (Distinguished Name): Specify at least one Subject Distinguished Name component for your self-signed certificate.

    • Common Name is selected as default, but you can delete the value by clicking the Clear icon and select another option from the drop-down list.

      

    • Alternatively, you can type the attribute's long or short name or OID directly into the field.

    • Click the Add Value button to include additional attributes of your Subject Distinguished Name in the self-signed certificate.

      

11. Key Usage: Use this section to specify the intended purpose of the certificate. The User Certificate template is pre-selected.

    

    You can select a template with pre-selected options, which you can edit, or choose the empty template to define the key usage from scratch.

    Click the drop-down button on the right do display key usage and extended key usage options.

    The available templates are:

    • Certificate Authority: You can use this template as a starting point if you selected a CA certificate as the basic constraint (see point 10.)

      

    • User Certificate (default)

      

    • Code Signing

      

    • OpenVPN Client

      

    • Empty

12. Other x509 v3 Extensions (Advanced): If you need x509 v3 extensions to be added to your certificate:

    1. Click the Other x509 v3 Extensions (Advanced) drop-down button.

       

    2. A list of most commonly used extensions will be displayed.

       

       If you want to add a custom extension to your certificate, see point 16.

    3. Click the toggle button to enable an extension in your certificate.

    4. A checkbox will appear to the left of the toggle button. If checked, the extension will be marked as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate..

       

       • Subject Alternative Name:

         • IP Address

         • DNS Name

         • Email

         • URI (Unique Resource Identifier)

         • UPN (User Principal Name)

         Hover over the information icon to view example entries for each type.

         Click the Add SAN button for additional SAN entries. The number of SANs is not limited.

       • CRL Distribution Points:

         Specify the HTTPS or LDAP endpoints' URLs where the Certificate Revocation List (CRL) can be accessed.

         Click the Add CRL button for additional CRL distribution point entries. The number of entries is not limited.

       • Subject Key Identifier

         This field is used to uniquely identify the certificate. Its value is typically the SHA-1 hash of the subject's public key.

         If not enabled, the correct value will be automatically filled in during generation. You may enter your own value for testing purposes.

       • Authority Information Access:

         This extension specifies the locations where information about the issuing Certificate Authority (CA) certificate can be found, typically HTTP or LDAP URIs.

         Select the access method to retrieve information about the CA certificate and enter the corresponding value:

         • OCSP: Specify the URI for the Online Certificate Status Protocol (OCSP) responder, which checks the revocation status of the certificate.

         • CA Issuer: Specify the URI for the issuing CA’s certificate.

    5. To remove an extension, click the trash bin icon .

13. To add custom extensions to your certificate, click the Add Custom Extension button in the Other x509 v3 Extensions (Advanced) field.

    1. The Custom Extension form will appear in the dialog:

       

    2. Enter a Name for the custom extension. This value is for informational purposes only.

    3. Enter the custom extension's object identifier (OID Object identifier. Globally unique identifiers standardized by the International Telecommunication Union. OIDs are represented as a series of numbers separated by dots (e.g., 2.5.29.37).) (e.g., 2.5.29.19).

    4. Add the extension's content in hexadecimal format.

    5. To mark an extension as critical If an extension is marked as critical, the extension must be understood and processed by any application that uses the certificate. If an application encounters a critical extension that it does not recognize or understand, it must reject the certificate., check the checkbox to the left of the toggle button.

       

    6. To remove an extension, click the trash bin icon .

14. Click the Generate button.

    The key with the generated certificate is now displayed in the respective slot tile.

    

Crescendo Manager allows you to generate Secure Key Injection Secure Key Injection is a FIPS certification-compliant protocol that ensures data protection when importing private keys, OTP secrets, and management keys. (SKI) Transport key pairs for your tokens. These key pairs can then be used for secure transfer of secrets to your tokens in compliance with the Secure Key Injection protocol.

To generate a new SKI Transport Key for the selected token:

1. Go to the Certificates view in the left navigation pane.

2. Click the Generate button in the top-right corner of the Certificates view

   

3. From the Select action drop-down, select New key.

   

4. Choose Key Slot: In the drop-down menu, select SKI Transport Key. The Key Type field will be set to RSA 3072 automatically.

   

5. Key Name: The key name is a human-readable string used to identify the key. Use the randomly generated value or overwrite it.

   Note:

   Knowing the key name is useful when you need to use the key directly, such as with the Cryptography Next Generation (CNG Cryptography Next Generation. A modern cryptographic API (Application Programming Interface) introduced by Microsoft as part of Windows to replace the older CryptoAPI. It provides a flexible and extensible framework for implementing cryptographic algorithms, key storage, and secure key management and supports a wide range of cryptographic operations, including encryption, decryption, hashing, and digital signatures.) application programming interface. See the simple PowerShell example below, which opens the key for further actions.

   Copy

   [System.Security.Cryptography.CngKey]::Open($keyname, [System.Security.Cryptography.CngProvider]::MicrosoftSmartCardKeyStorageProvider)

6. Click the Generate button. The new SKI Transport Key is now displayed as a new tile.

   

Exporting an SKI Transport Key

To copy the public part of an SKI Transport Key:

1. Click the SKI Transport Key tile.

2. Click Copy to Clipboard to copy and paste the public part of the SKI Transport Key into the desired application in PEM format.

   

3. Click Save to File to save the public part of the SKI Transport Key in PEM format to the selected destination.

What's Next

A generated SKI Transport Key can be used for encrypting secrets for Secure Key Injection with the SKI Wrapper tool.