Configuration parameters
This page describes the configuration parameters.
Customer-specific parameters
The following parameters are required to establish connection with SCM.
Parameter | Type | Description |
---|---|---|
|
Mandatory |
Your Sectigo username |
|
Mandatory |
Your Sectigo password |
|
Mandatory |
Your specific Sectigo URI |
|
Mandatory |
Your organization ID (numeric) |
|
Mandatory |
The base URL of the Sectigo Certificate Authority |
CSR parameters
The following parameters are required during the generation of the certificate signing request (CSR).
Parameter | Type | Description |
---|---|---|
|
Conditional |
A single value for a domain which is included in the certificate Common Name (CN) field |
|
Conditional |
The country name which is included in the certificate Country (C) field |
|
Conditional |
The state/province name which is included in the certificate State (ST) field |
|
Conditional |
The location name which is included in the certificate Location (L) field |
|
Conditional |
The organization name which is included in the certificate Organization (O) field |
|
Conditional |
The organization unit which is included in the certificate Organization Unit (OU) field |
|
Conditional |
The email address which is included in the certificate emailAddress field |
|
Conditional |
The full path of the certificate signing request file. If this is provided, then the subject parameters will be ignored. |
|
Optional |
The private key algorithm to use to generate the private key.
The default value is |
|
Optional |
The size of the TLS/SSL key to generate. The possible values are:
|
Certificate issuance parameters
The following parameters are used for certificate issuance. This operation supports different scenarios that require different parameters.
Parameter | Type | Description |
---|---|---|
SSL certificates |
||
|
Mandatory |
The location where the certificate, CSR, private key, and enrollment IDs are stored. |
|
Mandatory |
The name of the certificate file. The same name is used for the private key, CSR, and enrollment IDs. |
|
Mandatory |
The type of the SSL certificate. This is the ID of the SSL certificate type. |
|
Mandatory |
The certificate validity period in days.
The available values are dependent on |
|
Optional |
The format type for the SSL certificate. The allowed values are:
|
|
Optional |
Comments for certificate enrollment |
|
Conditional |
The number of server licenses |
|
Optional |
The custom fields to be applied to the requested certificate. The expected format for custom fields is the following.
If you are providing this input in a JSON string, make sure that the internal double quotes are escaped properly using |
|
Optional |
The server type ID |
|
Optional |
A comma-separated list of subject alternative names (SAN) |
|
Optional |
A comma-separated list of emails |
Client certificates |
||
|
Mandatory |
The location where the certificate, CSR, private key, and enrollment IDs are stored. |
|
Mandatory |
The name of the certificate file. The same name is used for the private key, the CSR, and enrollment IDs. |
|
Conditional |
The user’s first name |
|
Conditional |
The user’s middle name |
|
Conditional |
The user’s last name. The combined length of the first, middle, and last name fields cannot exceed 64 characters. |
|
Mandatory |
A valid user email that is less than 256 characters |
|
Mandatory |
The type of the certificate. This is the ID of the client certificate type. |
|
Mandatory |
The certificate validity period in days.
The available values depend on |
|
Optional |
A comma-separated list of subject alternative names (SAN) |
|
Optional |
The custom fields to be applied to the requested certificate. The expected format for custom fields is the following.
If you are providing this input in a JSON string, make sure that the internal double quotes are escaped properly using |
|
Mandatory |
If |
Certificate autorenewal |
||
|
Optional |
If |
|
Optional |
The period of days prior to expiration that a new client certificate enrollment process will be initiated if a |
Certificate collection parameters
The collection operation may fail if the certificate is still being processed. In such cases, the Sectigo SaltStack integration will try several times before returning a failure. The following parameters are used to configure the frequency and maximum time for additional attempts at certificate collection.
Parameter |
Type |
Description |
|
Optional |
The interval (in seconds) between repeated attempts to collect a certificate.
The default value is |
|
Optional |
The maximum time (in seconds) during which repeated attempts to collect a certificate will be made.
The default value is |
Certificate revocation parameters
Certificates can be manually revoked. In order to revoke a certificate, the following parameters are needed.
Parameter | Type | Description |
---|---|---|
SSL certificates |
||
|
Mandatory |
If |
Client certificates |
||
|
Mandatory |
If |
It is suggested that you set sectigo_ssl_cert_revoke
back to False
following the revocation of a certificate.
This will help prevent costs associated with unintended certificate revocations.
Other parameters
The following parameters are used to modify the behavior of the issuance operation.
Parameter | Type | Description |
---|---|---|
|
Optional |
Used to issue a new certificate even if there is already a certificate on the target server.
The default value is If |
|
Mandatory |
Set the target value.
For example, if you want to deploy the certificate to a group of minions with similar hostname prefix ( |
|
Mandatory |
The reason why a certificate is to be revoked or replaced |
SaltStack CLI parameters
The following parameters are used in the CLI commands directly.
Parameter | Description |
---|---|
|
The |
|
Can be either |
|
The config file from the |
|
The host name of the minions (such as Note that you can also use wildcard if there is more than one minion with a similar prefix which needs to have the exact configuration.
For example, if there are 3 minions with the names: The target is case sensitive and must match the minion hostname exactly. |