TLS Connect Software Configuration
Atlas Account
To use TLS Connect with your Atlas account or the Atlas ACME server, you must first configure your Atlas credentials and authentication settings.
- Open the TLS Connect application and navigate to Settings > Atlas Configuration.
- Click Add New Service and enter a friendly name and your Atlas API key and API secret. If you do not already have Atlas API credentials, refer to this support article↗ for instructions on generating an API key and secret.
- Configure Atlas mTLS authentication, which TLS Connect uses to securely communicate with Atlas.
- Select No (Generate CSR) and then click Generate Certificate Request to have TLS Connect generate a Certificate Signing Request (CSR).
- Copy and paste the CSR content in the Atlas portal to request an mTLS certificate. For detailed steps on requesting an mTLS certificate in Atlas, refer to this support article↗.
- Copy and paste the resulting mTLS certificate into a .txt file.
- Back in TLS Connect, paste the contents of the mTLS certificate into the “Step 2” text field and then click Import Certificate.
- Choose the imported certificate from the “Select Certificate” dropdown menu.
- You may choose to make this linked service the default service.
- You may verify that your credentials are correctly linked to TLS Connect by clicking Test Login.
- Select Yes (Import PFX) and then click Import PFX Certificate.
- Upload the .pfx file.
- You may choose to make this linked service the default service.
Once the configuration is saved, TLS Connect is ready to request, issue, and deploy TLS certificates using your Atlas account.
ACME Service
To use TLS Connect with the Atlas ACME server, you must first configure your Atlas credentials and authentication settings as described in the previous section. You must also update the simple-acme configuration to align with your Atlas certificate service. Once these steps are complete, configure TLS Connect with your Atlas ACME account details.
- Ensure simple-acme is installed on the same server as TLS Connect.
- If you have not already done so, download and install the latest version of simple-acme↗.
- Navigate to the installation directory for the wacs.exe simple-acme client and open the settings.json file in a text editor.
- Change the CSR values to match the GlobalSign Atlas certificate service you have purchased:
- For RSA product packs:
- Set SignatureAlgorithm to SHA256withRSA or SHA384withRSA.
- Set the KeyBits field to 256.
- For ECC product packs:
- Set SignatureAlgorithm to SHA384withECDSA.
- Set the KeyBits field to 256.
- For RSA product packs:
- You may optionally change the CertificateStore.PrivateKeyExportable field to TRUE to enable private key export. The default value is FALSE.
- You may optionally change the Renewal Days value to trigger certificate renewals at a specified number of days into a certificate’s lifetime. The default value is 55.
- Save and close the settings.json file.
- Open the TLS Connect application and navigate to Settings > ACME Configuration.
- Browse and enter the file path to the simple-acme client, then click Save.
- Enter the required ACME account details:
- Account Name (Company name)
- Email address
- EAB Key (Atlas API key)
- EAB HMAC Key (Atlas ACME HMAC key)
- Click Add Account to create the ACME account.
- The newly added account appears in the Accounts table at the bottom of the screen. Click Register to activate the ACME account for use by TLS Connect.
WHAT'S NEXT: Once the configuration is saved, TLS Connect is ready to request, issue, and deploy TLS certificates using the ACME protocol with your Atlas account. To manage certificate, please refer to this page↗.