Configuring the plugin
The Sectigo Jenkins plugin requires that certain variables are provided. The variables required are dependent on the specific use case. These values need to be provided in the configuration file that can be either in YAML or JSON format. Some values can also be provided in the Jenkins pipeline or Jenkinsfile as parameters when a certificate operation is requested.
The following tables list the parameters that can be used with the available configurations.
Customer-specific parameters
The following parameters are required to establish connection with SCM.
Parameter | Description |
---|---|
|
User ID to access your URL |
|
Password to access your URL |
|
Your Sectigo URI |
|
Your Organization ID (numeric) |
|
The base URL of the Sectigo Certificate Authority. If provided, the host name will be extracted and used. Required if |
|
The host name of the Sectigo Certificate Authority. Required if |
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. Required if |
|
Conditional |
This parameter can be provided instead of specifying each CSR parameter individually.
If specified, the default values will be used for Required if |
|
Conditional |
The country name which is included in the certificate Country (C) field. Required if |
|
Conditional |
The state/province name which is included in the certificate State (ST) field. Required if |
|
Conditional |
The location name included in the certificate Location (L) field. Required if |
|
Conditional |
The organization name included in the certificate Organization (O) field. Required if |
|
Conditional |
The organization unit included in the certificate Organization Unit (OU) field. Required if |
|
Conditional |
The email address which is included in the certificate emailAddress field. Required if |
|
Conditional |
The full path to the CSR file. If this is provided, the subject parameters are ignored. |
|
Optional |
The private key algorithm used to generate the private key.
The default value is |
|
Optional |
The size of the TLS/SSL keys 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 |
---|---|---|
Certificate issuance |
||
|
Optional |
The location where the certificate is to be stored. The same location is used to store the CSR, private key, and enrollment IDs. The default is the config file’s path. |
|
Mandatory |
The name of the certificate file. The same name is used for the CSR, private key, and enrollment IDs.
The default value is |
|
Mandatory |
The type of SSl certificate (numeric). This is the ID of the SSL certificate type. |
|
Mandatory |
The certificate validity period in days (numeric).
The values are dependent on the selected |
|
Conditional |
The number of server licenses (numeric) |
|
Optional |
A comma-separated list of subject alternative names (SAN) |
|
Optional |
A comma-separated list of emails |
|
Optional |
The format type for the SSL certificate. The supported values are:
|
|
Optional |
Comments for certificate enrollment |
|
Optional |
The custom fields to be applied to 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 (numeric). |
Auto-renewal |
||
|
Optional |
If you do not want to automatically renew certificates, you must specify |
|
Conditional |
The period of days prior to expiration that a new SSL certificate enrollment process will be initiated if an issue operation is started. The default expiry window is |
Certificate collection parameters
The collection operation may fail if the certificate is still being processed. In such cases, the Sectigo Jenkins 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 renewal and revocation parameters
Certificates can be manually renewed or revoked. In such cases the following parameters are needed.
Parameter | Type | Description |
---|---|---|
|
Mandatory |
The ID of the SSL certificate to be renewed or revoked. |
|
Mandatory |
The reason why a certificate is to be revoked. This parameter is required for the revoke operation. |
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 |
|
Optional |
Used to collect the certificate even if a valid certificate is already available.
The default value is If |
Jenkins pipeline parameters
The following parameters are used for the call in Jenkins. Some of these parameters can be provided from the configuration file.
Parameter | Description |
---|---|
|
The operation to be performed. The supported values are:
Must be provided in the Jenkinsfile/Jenkins pipeline when the plugin is called. |
|
The configuration file’s name and location. Must be provided in the Jenkinsfile/Jenkins pipeline when the plugin is called. |
|
The format of the configuration file. The supported formats are JSON and YAML. Must be provided in the Jenkinsfile/Jenkins pipeline when the plugin is called. |
|
The For more information on |
|
The host name of the Sectigo Certificate Authority. Alternatively, this parameter can be provided in the configuration file through the |
|
Your specific SCM URI. Alternatively, this parameter can be provided in the configuration file through the |
|
User ID to access your SCM URI. Alternatively, this parameter can be provided in the configuration file through the |
|
Password to access your SCM URI. Alternatively, this parameter can be provided in the configuration file through the |