GlobalSign Certificate Provider

The GlobalSign certificate provider allows you to request certificates through the GMO GlobalSign Atlas portal. GlobalSign is a public CA that issues TLS server and S/MIME certificates, among other types of certificates. A valid and active account at the Atlas-Portal of GlobalSign is required for using the GlobalSign certificate provider. You can then retrieve secrets and keys, to connect to the GlobalSign CA and request certificates.

By using a certificate provider type of GlobalSign, the GlobalSign related fields become available for modification as well. The Update Keystore button allows the entry of a new GlobalSign Keystore and Keystore Password. Selecting Cancel will return the Keystore values to the original ones. Otherwise, the certificate provider updates upon clicking the Proceed button.

Below you will find which parameters are required for the creation of a GlobalSign certificate provider.

GlobalSign certificate provider required parameters
Parameter	Description
GlobalSign API URL	URL where a GlobalSign instance is running default→emea.api.hvca.globalsign.com:8443/v2 🔗
GlobalSign Intended Use	refers to the purpose of the certificate
GlobalSign API Key and GlobalSign API Secret	credentials linked with a GlobalSign account
GlobalSign Keystore	needed to perform mTLS with GlobalSign server for given account
GlobalSign Keystore Password	the password of GlobalSign Keystore
GlobalSign Proxy Host & GlobalSign Proxy Port	refer to the address and port of the proxy server to be used

Some certificate request modes, cryptographic algorithms and ERS component might not be compatible with GlobalSign certificate provider. For more details, see here 🔗

DNS Validation

MTG CLM supports DNS TXT validation for GlobalSign certificates. This validation method requires creating DNS TXT records for your domain, in order to prove domain ownership. DNS TXT validation enables certificate issuance for wildcard domains and scenarios where HTTP-based validation cannot be performed.

Domain validation and other validations are performed outside the CLM platform. CLM serves solely to request the certificate. For a successful certificate request, the requirements regarding validation must be met.