community.crypto.openssl_csr_pipe module – Generate OpenSSL Certificate Signing Request (CSR)
Note
This module is part of the community.crypto collection (version 2.16.1).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.crypto
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.crypto.openssl_csr_pipe
.
New in community.crypto 1.3.0
Synopsis
Please note that the module regenerates an existing CSR if it does not match the module’s options, or if it seems to be corrupt.
This module allows one to (re)generate OpenSSL certificate signing requests.
This module supports the subjectAltName, keyUsage, extendedKeyUsage, basicConstraints and OCSP Must Staple extensions.
Requirements
The below requirements are needed on the host that executes this module.
cryptography >= 1.3
Parameters
Parameter |
Comments |
---|---|
Names that will be present in the authority cert issuer field of the certificate signing request. Values must be prefixed by their options. (That is, Example: If specified, Please note that commercial CAs ignore this value, respectively use a value of their own choice. Specifying this option is mostly useful for self-signed certificates or for own CAs. Note that this is only supported if the The |
|
The authority cert serial number. If specified, Note that this is only supported if the Please note that commercial CAs ignore this value, respectively use a value of their own choice. Specifying this option is mostly useful for self-signed certificates or for own CAs. The |
|
The authority key identifier as a hex string, where two bytes are separated by colons. Example: Please note that commercial CAs ignore this value, respectively use a value of their own choice. Specifying this option is mostly useful for self-signed certificates or for own CAs. Note that this is only supported if the The |
|
Indicates basic constraints, such as if the certificate is a CA. |
|
Should the basicConstraints extension be considered as critical. Choices:
|
|
The commonName field of the certificate signing request subject. |
|
The existing CSR. |
|
The countryName field of the certificate signing request subject. |
|
Create the Subject Key Identifier from the public key. Please note that commercial CAs can ignore the value, respectively use a value of their own choice instead. Specifying this option is mostly useful for self-signed certificates or for own CAs. Note that this is only supported if the Choices:
|
|
Allows to specify one or multiple CRL distribution points. Only supported by the |
|
Information about the issuer of the CRL. |
|
Describes how the CRL can be retrieved. Mutually exclusive with Example: |
|
List of reasons that this distribution point can be used for when performing revocation checks. Choices:
|
|
Describes how the CRL can be retrieved relative to the CRL issuer. Mutually exclusive with Example: Can only be used when cryptography >= 1.6 is installed. |
|
The digest used when signing the certificate signing request with the private key. Default: |
|
The emailAddress field of the certificate signing request subject. |
|
Additional restrictions (for example client authentication, server authentication) on the allowed purposes for which the public key may be used. |
|
Should the extkeyUsage extension be considered as critical. Choices:
|
|
This defines the purpose (for example encipherment, signature, certificate signing) of the key contained in the certificate. |
|
Should the keyUsage extension be considered as critical. Choices:
|
|
The localityName field of the certificate signing request subject. |
|
Should the Name Constraints extension be considered as critical. Choices:
|
|
For CA certificates, this specifies a list of identifiers which describe subtrees of names that this CA is not allowed to issue certificates for. Values must be prefixed by their options. (That is, |
|
For CA certificates, this specifies a list of identifiers which describe subtrees of names that this CA is allowed to issue certificates for. Values must be prefixed by their options. (That is, |
|
Indicates that the certificate should contain the OCSP Must Staple extension (https://tools.ietf.org/html/rfc7633). Choices:
|
|
Should the OCSP Must Staple extension be considered as critical. Note that according to the RFC, this extension should not be marked as critical, as old clients not knowing about OCSP Must Staple are required to reject such certificates (see https://tools.ietf.org/html/rfc7633#section-4). Choices:
|
|
The organizationName field of the certificate signing request subject. |
|
The organizationalUnitName field of the certificate signing request subject. |
|
The content of the private key to use when signing the certificate signing request. Either |
|
The passphrase for the private key. This is required if the private key is password protected. |
|
The path to the private key to use when signing the certificate signing request. Either |
|
Determines which crypto backend to use. The default choice is If set to Choices:
|
|
The stateOrProvinceName field of the certificate signing request subject. |
|
Key/value pairs that will be present in the subject name field of the certificate signing request. If you need to specify more than one value with the same key, use a list as value. If the order of the components is important, use Mutually exclusive with |
|
Subject Alternative Name (SAN) extension to attach to the certificate signing request. Values must be prefixed by their options. (These are Note that if no SAN is specified, but a common name, the common name will be added as a SAN except if More at https://tools.ietf.org/html/rfc5280#section-4.2.1.6. |
|
Should the subjectAltName extension be considered as critical. Choices:
|
|
The subject key identifier as a hex string, where two bytes are separated by colons. Example: Please note that commercial CAs ignore this value, respectively use a value of their own choice. Specifying this option is mostly useful for self-signed certificates or for own CAs. Note that this option can only be used if Note that this is only supported if the |
|
A list of dictionaries, where every dictionary must contain one key/value pair. This key/value pair will be present in the subject name field of the certificate signing request. If you want to specify more than one value with the same key in a row, you can use a list as value. Mutually exclusive with |
|
If set to Choices:
|
|
The version of the certificate signing request. The only allowed value according to RFC 2986 is 1. This option no longer accepts unsupported values since community.crypto 2.0.0. Choices:
|
Attributes
Attribute |
Support |
Description |
---|---|---|
Support: full |
Can run in |
|
Support: full |
Will return details on what has changed (or possibly needs changing in |
Notes
Note
If the certificate signing request already exists it will be checked whether subjectAltName, keyUsage, extendedKeyUsage and basicConstraints only contain the requested values, whether OCSP Must Staple is as requested, and if the request was signed by the given private key.
See Also
See also
- community.crypto.openssl_csr
Generate OpenSSL Certificate Signing Request (CSR).
- community.crypto.x509_certificate
Generate and/or check OpenSSL certificates.
- community.crypto.x509_certificate_pipe
Generate and/or check OpenSSL certificates.
- community.crypto.openssl_dhparam
Generate OpenSSL Diffie-Hellman Parameters.
- community.crypto.openssl_pkcs12
Generate OpenSSL PKCS#12 archive.
- community.crypto.openssl_privatekey
Generate OpenSSL private keys.
- community.crypto.openssl_privatekey_pipe
Generate OpenSSL private keys without disk access.
- community.crypto.openssl_publickey
Generate an OpenSSL public key from its private key.
- community.crypto.openssl_csr_info
Provide information of OpenSSL Certificate Signing Requests (CSR).
Examples
- name: Generate an OpenSSL Certificate Signing Request
community.crypto.openssl_csr_pipe:
privatekey_path: /etc/ssl/private/ansible.com.pem
common_name: www.ansible.com
register: result
- name: Print CSR
ansible.builtin.debug:
var: result.csr
- name: Generate an OpenSSL Certificate Signing Request with an inline CSR
community.crypto.openssl_csr:
content: "{{ lookup('ansible.builtin.file', '/etc/ssl/csr/www.ansible.com.csr') }}"
privatekey_content: "{{ private_key_content }}"
common_name: www.ansible.com
register: result
- name: Store CSR
ansible.builtin.copy:
dest: /etc/ssl/csr/www.ansible.com.csr
content: "{{ result.csr }}"
when: result is changed
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Indicates if the certificate belongs to a CA Returned: changed or success Sample: |
|
The (current or generated) CSR’s content. Returned: changed or success |
|
Additional restriction on the public key purposes Returned: changed or success Sample: |
|
Purpose for which the public key may be used Returned: changed or success Sample: |
|
List of excluded subtrees the CA cannot sign certificates for. Returned: changed or success Sample: |
|
List of permitted subtrees to sign certificates for. Returned: changed or success Sample: |
|
Indicates whether the certificate has the OCSP Must Staple feature enabled Returned: changed or success Sample: |
|
Path to the TLS/SSL private key the CSR was generated for Will be Returned: changed or success Sample: |
|
A list of the subject tuples attached to the CSR Returned: changed or success Sample: |
|
The alternative names this CSR is valid for Returned: changed or success Sample: |