+ |
+The path to the accountkey for the acme provider.
+ This is only used by the acme provider.
+ |
+
+ |
+Include the intermediate certificate to the generated certificate
+ This is only used by the acme provider.
+ Note that this is only available for older versions of acme-tiny . New versions include the chain automatically, and setting acme_chain to true results in an error.
+ Choices:
+
+false ← (default)
+true
+
+ |
+
+ |
+ |
+
+
+
+ string
+ added in community.crypto 1.0.0
+ |
+The ACME directory to use. You can use any directory that supports the ACME protocol, such as Buypass or Let’s Encrypt.
+ Let’s Encrypt recommends using their staging server while developing jobs. https://letsencrypt.org/docs/staging-environment/.
+ Default: "https://acme-v02.api.letsencrypt.org/directory"
+ |
+
+
+
+
+ aliases: attr
+ string
+ |
+The attributes the resulting filesystem object should have.
+ To get supported flags look at the man page for chattr on the target system.
+ This string should contain the attributes in the same order as the one displayed by lsattr.
+ The = operator is assumed as default, otherwise + or - operators need to be included in the string.
+ |
+
+ |
+Create a backup file including a timestamp so you can get the original certificate back if you overwrote it with a new one by accident.
+ Choices:
+
+false ← (default)
+true
+
+ |
+
+
+
+ string
+ added in community.crypto 1.0.0
+ |
+Content of the Certificate Signing Request (CSR) used to generate this certificate.
+ This is mutually exclusive with csr_path .
+ |
+
+ |
+Path to the Certificate Signing Request (CSR) used to generate this certificate.
+ This is mutually exclusive with csr_content .
+ |
+
+ |
+The path to the private key of the client certificate used to authenticate to the Entrust Certificate Services (ECS) API.
+ This is only used by the entrust provider.
+ This is required if the provider is entrust .
+ |
+
+ |
+The path to the client certificate used to authenticate to the Entrust Certificate Services (ECS) API.
+ This is only used by the entrust provider.
+ This is required if the provider is entrust .
+ |
+
+ |
+The key (password) for authentication to the Entrust Certificate Services (ECS) API.
+ This is only used by the entrust provider.
+ This is required if the provider is entrust .
+ |
+
+ |
+The path to the specification file defining the Entrust Certificate Services (ECS) API configuration.
+ You can use this to keep a local copy of the specification to avoid downloading it every time the module is used.
+ This is only used by the entrust provider.
+ Default: "https://cloud.entrust.net/EntrustCloud/documentation/cms-api-2.1.0.yaml"
+ |
+
+ |
+The username for authentication to the Entrust Certificate Services (ECS) API.
+ This is only used by the entrust provider.
+ This is required if the provider is entrust .
+ |
+
+ |
+Specify the type of certificate requested.
+ This is only used by the entrust provider.
+ Choices:
+
+ |
+
+ |
+The point in time at which the certificate stops being valid.
+ Time can be specified either as relative time or as an absolute timestamp.
+ A valid absolute time format is ASN.1 TIME such as 2019-06-18 .
+ A valid relative time format is [+-]timespec where timespec can be an integer + [w | d | h | m | s] , such as +365d or +32w1d2h ).
+ Time will always be interpreted as UTC.
+ Note that only the date (day, month, year) is supported for specifying the expiry date of the issued certificate.
+ The full date-time is adjusted to EST (GMT -5:00) before issuance, which may result in a certificate with an expiration date one day earlier than expected if a relative time is used.
+ The minimum certificate lifetime is 90 days, and maximum is three years.
+ If this value is not specified, the certificate will stop being valid 365 days the date of issue.
+ This is only used by the entrust provider.
+ Please note that this value is not covered by the ignore_timestamps option.
+ Default: "+365d"
+ |
+
+ |
+The email of the requester of the certificate (for tracking purposes).
+ This is only used by the entrust provider.
+ This is required if the provider is entrust .
+ |
+
+ |
+The name of the requester of the certificate (for tracking purposes).
+ This is only used by the entrust provider.
+ This is required if the provider is entrust .
+ |
+
+ |
+The phone number of the requester of the certificate (for tracking purposes).
+ This is only used by the entrust provider.
+ This is required if the provider is entrust .
+ |
+
+ |
+Generate the certificate, even if it already exists.
+ Choices:
+
+false ← (default)
+true
+
+ |
+
+ |
+Name of the group that should own the filesystem object, as would be fed to chown.
+ When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.
+ |
+
+
+
+ boolean
+ added in community.crypto 2.0.0
+ |
+Whether the “not before” and “not after” timestamps should be ignored for idempotency checks.
+ It is better to keep the default value true when using relative timestamps (like +0s for now).
+ Choices:
+
+false
+true ← (default)
+
+ |
+
+ |
+The permissions the resulting filesystem object should have.
+ For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777' ) so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755 ) works sometimes, but can fail in loops and some other circumstances.
+ Giving Ansible a number without following either of these rules will end up with a decimal number which will have unexpected results.
+ As of Ansible 1.8, the mode may be specified as a symbolic mode (for example, u+rwx or u=rw,g=r,o=r ).
+ If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.
+ If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.
+ Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.
+ |
+
+
+
+ string
+ added in community.crypto 1.0.0
+ |
+Content of the CA (Certificate Authority) certificate.
+ This is only used by the ownca provider.
+ This is mutually exclusive with ownca_path .
+ |
+
+ |
+Create a Authority Key Identifier from the CA’s certificate. If the CSR provided a authority key identifier, it is ignored.
+ The Authority Key Identifier is generated from the CA certificate’s Subject Key Identifier, if available. If it is not available, the CA certificate’s public key will be used.
+ This is only used by the ownca provider.
+ Note that this is only supported if the cryptography backend is used!
+ Choices:
+
+false
+true ← (default)
+
+ |
+
+ |
+Whether to create the Subject Key Identifier (SKI) from the public key.
+ A value of create_if_not_provided (default) only creates a SKI when the CSR does not provide one.
+ A value of always_create always creates a SKI. If the CSR provides one, that one is ignored.
+ A value of never_create never creates a SKI. If the CSR provides one, that one is used.
+ This is only used by the ownca provider.
+ Note that this is only supported if the cryptography backend is used!
+ Choices:
+
+ |
+
+ |
+The digest algorithm to be used for the ownca certificate.
+ This is only used by the ownca provider.
+ Default: "sha256"
+ |
+
+ |
+The point in time at which the certificate stops being valid.
+ Time can be specified either as relative time or as absolute timestamp.
+ Time will always be interpreted as UTC.
+ Valid format is [+-]timespec | ASN.1 TIME where timespec can be an integer + [w | d | h | m | s] (for example +32w1d2h ).
+ If this value is not specified, the certificate will stop being valid 10 years from now.
+ Note that this value is not used to determine whether an existing certificate should be regenerated. This can be changed by setting the ignore_timestamps option to false . Please note that you should avoid relative timestamps when setting ignore_timestamps=false .
+ This is only used by the ownca provider.
+ On macOS 10.15 and onwards, TLS server certificates must have a validity period of 825 days or fewer. Please see https://support.apple.com/en-us/HT210176 for more details.
+ Default: "+3650d"
+ |
+
+ |
+The point in time the certificate is valid from.
+ Time can be specified either as relative time or as absolute timestamp.
+ Time will always be interpreted as UTC.
+ Valid format is [+-]timespec | ASN.1 TIME where timespec can be an integer + [w | d | h | m | s] (for example +32w1d2h ).
+ If this value is not specified, the certificate will start being valid from now.
+ Note that this value is not used to determine whether an existing certificate should be regenerated. This can be changed by setting the ignore_timestamps option to false . Please note that you should avoid relative timestamps when setting ignore_timestamps=false .
+ This is only used by the ownca provider.
+ Default: "+0s"
+ |
+
+ |
+Remote absolute path of the CA (Certificate Authority) certificate.
+ This is only used by the ownca provider.
+ This is mutually exclusive with ownca_content .
+ |
+
+
+
+ string
+ added in community.crypto 1.0.0
+ |
+Content of the CA (Certificate Authority) private key to use when signing the certificate.
+ This is only used by the ownca provider.
+ This is mutually exclusive with ownca_privatekey_path .
+ |
+
+ |
+ |
+
+ |
+Path to the CA (Certificate Authority) private key to use when signing the certificate.
+ This is only used by the ownca provider.
+ This is mutually exclusive with ownca_privatekey_content .
+ |
+
+ |
+The version of the ownca certificate.
+ Nowadays it should almost always be 3 .
+ This is only used by the ownca provider.
+ Default: 3
+ |
+
+ |
+Name of the user that should own the filesystem object, as would be fed to chown.
+ When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.
+ Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.
+ |
+
+ |
+Remote absolute path where the generated certificate file should be created or is already located.
+ |
+
+
+
+ string
+ added in community.crypto 1.0.0
+ |
+Content of the private key to use when signing the certificate.
+ This is mutually exclusive with privatekey_path .
+ |
+
+ |
+ |
+
+ |
+Path to the private key to use when signing the certificate.
+ This is mutually exclusive with privatekey_content .
+ |
+
+ |
+ |
+
+
+
+ boolean
+ added in community.crypto 1.0.0
+ |
+If set to true , will return the (current or generated) certificate’s content as certificate .
+ Choices:
+
+false ← (default)
+true
+
+ |
+
+ |
+Determines which crypto backend to use.
+ The default choice is auto , which tries to use cryptography if available.
+ If set to cryptography , will try to use the cryptography library.
+ Choices:
+
+"auto" ← (default)
+"cryptography"
+
+ |
+
+ |
+The level part of the SELinux filesystem object context.
+ This is the MLS/MCS attribute, sometimes known as the range .
+ When set to _default , it will use the level portion of the policy if available.
+ |
+
+ |
+Whether to create the Subject Key Identifier (SKI) from the public key.
+ A value of create_if_not_provided (default) only creates a SKI when the CSR does not provide one.
+ A value of always_create always creates a SKI. If the CSR provides one, that one is ignored.
+ A value of never_create never creates a SKI. If the CSR provides one, that one is used.
+ This is only used by the selfsigned provider.
+ Note that this is only supported if the cryptography backend is used!
+ Choices:
+
+ |
+
+ |
+Digest algorithm to be used when self-signing the certificate.
+ This is only used by the selfsigned provider.
+ Default: "sha256"
+ |
+
+
+
+
+ aliases: selfsigned_notAfter
+ string
+ |
+The point in time at which the certificate stops being valid.
+ Time can be specified either as relative time or as absolute timestamp.
+ Time will always be interpreted as UTC.
+ Valid format is [+-]timespec | ASN.1 TIME where timespec can be an integer + [w | d | h | m | s] (for example +32w1d2h ).
+ If this value is not specified, the certificate will stop being valid 10 years from now.
+ Note that this value is not used to determine whether an existing certificate should be regenerated. This can be changed by setting the ignore_timestamps option to false . Please note that you should avoid relative timestamps when setting ignore_timestamps=false .
+ This is only used by the selfsigned provider.
+ On macOS 10.15 and onwards, TLS server certificates must have a validity period of 825 days or fewer. Please see https://support.apple.com/en-us/HT210176 for more details.
+ Default: "+3650d"
+ |
+
+
+
+
+ aliases: selfsigned_notBefore
+ string
+ |
+The point in time the certificate is valid from.
+ Time can be specified either as relative time or as absolute timestamp.
+ Time will always be interpreted as UTC.
+ Valid format is [+-]timespec | ASN.1 TIME where timespec can be an integer + [w | d | h | m | s] (for example +32w1d2h ).
+ If this value is not specified, the certificate will start being valid from now.
+ Note that this value is not used to determine whether an existing certificate should be regenerated. This can be changed by setting the ignore_timestamps option to false . Please note that you should avoid relative timestamps when setting ignore_timestamps=false .
+ This is only used by the selfsigned provider.
+ Default: "+0s"
+ |
+
+ |
+Version of the selfsigned certificate.
+ Nowadays it should almost always be 3 .
+ This is only used by the selfsigned provider.
+ Default: 3
+ |
+
+ |
+The role part of the SELinux filesystem object context.
+ When set to _default , it will use the role portion of the policy if available.
+ |
+
+ |
+The type part of the SELinux filesystem object context.
+ When set to _default , it will use the type portion of the policy if available.
+ |
+
+ |
+The user part of the SELinux filesystem object context.
+ By default it uses the system policy, where applicable.
+ When set to _default , it will use the user portion of the policy if available.
+ |
+
+ |
+Whether the certificate should exist or not, taking action if the state is different from what is stated.
+ Choices:
+
+"absent"
+"present" ← (default)
+
+ |
+
+ |
+Influence when to use atomic operation to prevent data corruption or inconsistent reads from the target filesystem object.
+ By default this module uses atomic operations to prevent data corruption or inconsistent reads from the target filesystem objects, but sometimes systems are configured or just broken in ways that prevent this. One example is docker mounted filesystem objects, which cannot be updated atomically from inside the container and can only be written in an unsafe manner.
+ This option allows Ansible to fall back to unsafe methods of updating filesystem objects when atomic operations fail (however, it doesn’t force Ansible to perform unsafe writes).
+ IMPORTANT! Unsafe writes are subject to race conditions and can lead to data corruption.
+ Choices:
+
+false ← (default)
+true
+
+ |
+
+
+