SignServer Cloud AWS
- AWS Launch Guide
- Quick Start Guide
- AWS Backup Guide
- AWS Restore and Upgrade Guide
- AWS TLS Certificate Generation Guide
- AWS Cluster Configuration Guide
Peering to EJBCA Cloud AWS Configuration Guide
- AWS Operating Environment
- EJBCA/SignServer Peering Security Groups
- Generate TLS Certificates for SignServer
- Allow Peer Connections in SignServer
- Peer Connection Configuration
- Creating the Peer Connection
- Allow Peer Connection in SignServer
- Configuring Automatic Generation and Key Renewal over Peers
- Automatically Renewing the Key Binding Key
SignServer CloudHSM Integration Guide
- Multiple Crypto Tokens with AWS CloudHSM
- Create a CloudHSM Cluster
- Use OpenSSL to Validate the HSM
- Initialize the CloudHSM
- Assigning Security Group
- Configure the cloudhsm-client
- PKCS11 PIN
- Activate Cluster
- Create a CloudHSM Crypto User
- Create Keystore in HSM with ClientToolBox
- Test with EJBCA ClientToolBox
- Create CryptoToken in SignServer
- Restoring HSM Backup to New Instance
SignServer Cloud Azure
- Azure Launch Guide
- Azure Key Vault Integration Guide
- SignServer Cloud Release Notes
Creating an App Registration in Active Directory
The following shows you how to add and register an application using App registrations in the Azure portal and then how to generate a secret (password), needed when obtaining tokens.
Registering the App in Active Directory and Generating Secret
- Login and access your Azure portal at https://portal.azure.com.
- Select the Azure Active Directory service in the left-hand navigation pane, and then select App registrations > New registration.
Specify an app name (that will be displayed to users of the app), for example "signserver-vault", and then click Register.
Azure AD assigns a unique application (client) ID to your app and displays your application's Overview page.
- On the Overview page, make a note of the Application (client) ID. This value will be required in SignServer when creating a Crypto Token.
- Click Certificates & secrets to add a secret (password).
- Click New client secret in the Client secrets section.
- Enter a name for the secret, such as "signserver-vault-access". Set the expiration if desired. In this example, the expiration is set to Never expire to allow the CA to always have access to the keys in the HSM. Click Add once done.
- A secret is generated and displayed. Note this secret down in a password manager such as Last Pass as it will only be displayed once in the portal. The secret will also be required in SignServer when creating a Crypto Token in the later step Creating an Azure Key Vault Crypto Token in SignServer.
Next, continue with Creating the Azure Key Vault.