Skip to main content
Skip table of contents

Creating an Azure Key Vault Crypto Token in SignServer

The following provides instructions for creating an Azure Key Vault Crypto Token in SignServer and how to manually activate the newly created Crypto Token if required.

Configuring Crypto Token

To create an Azure Key Vault Crypto Token in SignServer, do the following:

  1. Select the SignServer AdminWeb Workers tab, and click Add.
  2. Click From Template, select the azurekeyvault-crypto.properties template in the list, and click Next.
  3. Change the following properties to the values that reflect your key vault.
    1. WORKERGENID1.KEY_VAULT_NAME: In this example, SignServerKeyVault as specified when Creating an Azure Key Vault.
    2. WORKERGENID1.KEY_VAULT_CLIENT_ID: The Application (client) ID as noted down from the Overview page when creating the App Registration.
    3. WORKERGENID1.KEY_VAULT_TYPE: As selected when when Creating an Azure Key Vault, for example, Premium.
    4. WORKERGENID1.PIN: The client secret generated during the App Registration step. Uncomment this row and add the client secret signserver-vault-access value if you want the Crypto Token to auto-activate. To activate the token manually, see Manually Activating Crypto Token.
    5. WORKERGENID1.DEFAULTKEY: The name of the first key that SignServer uses to activate the Crypto Token. The key can be created in the Azure Key Vault user interface according to the previous step Creating First Key for SignServer.
  4. Click Apply to add the Crypto Token.
  5. The Crypto Token is displayed in the list as Active if the client secret was added as the PIN in the previous step.

Manually Activating Crypto Token

If the configured Crypto Token is not activated, do the following to manually activate the token:

  1. Select the newly created Crypto Token Azure Key Vault.
  2. Click the Crypto Token tab.
  3. Click Activate and add the client secret generated during the App Registration step.
  4. Click Activate to activate the Crypto Token.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.