-name:Check whether an account with the given account key existscommunity.crypto.acme_account_info:account_key_src:/etc/pki/cert/private/account.key
@@ -433,7 +433,7 @@ see
-
-name:Make sure account exists and has given contacts. We agree to TOS.community.crypto.acme_account:account_key_src:/etc/pki/cert/private/account.key
@@ -541,7 +541,7 @@ see
-
Create and renew SSL/TLS certificates with a CA supporting the ACME protocol, such as Let’s Encrypt or Buypass. The current implementation supports the http-01, dns-01 and tls-alpn-01 challenges.
To use this module, it has to be executed twice. Either as two different tasks in the same run or during two runs. Note that the output of the first run needs to be recorded and passed to the second run as the module argument data.
Prepares certificates for ACME challenges such as tls-alpn-01.
The raw data is provided by the community.crypto.acme_certificate module, and needs to be converted to a certificate to be used for challenge validation. This module provides a simple way to generate the required certificates.
-name:Create challenges for a given CRT for sample.comcommunity.crypto.acme_certificate:account_key_src:/etc/pki/cert/private/account.key
@@ -343,7 +343,7 @@ see
-
Allows to send direct requests to an ACME server with the ACME protocol, which is supported by CAs such as Let’s Encrypt.
This module can be used to debug failed certificate request attempts, for example when community.crypto.acme_certificate fails or encounters a problem which you wish to investigate.
This module completes a given chain of certificates in PEM format by finding intermediate certificates from a given set of certificates, until it finds a root certificate in another given set of certificates.
# Given a leaf certificate for www.ansible.com and one or more intermediate# certificates, finds the associated root certificate.-name:Find root certificate
@@ -309,7 +309,7 @@ see
-
Retrieve information on cryptographic capabilities.
The current version retrieves information on the Python cryptography library available to Ansible modules, and on the OpenSSL binary openssl found in the path.
The community.crypto collection offers multiple modules that create private keys, certificate signing requests, and certificates. This guide shows how to create your own small CA and how to use it to sign certificates.
In all examples, we assume that the CA’s private key is password protected, where the password is provided in the secret_ca_passphrase variable.
Any certificate can be used as a CA certificate. You can create a self-signed certificate (see How to create self-signed certificates), use another CA certificate to sign a new certificate (using the instructions below for signing a certificate), ask (and pay) a commercial CA to sign your CA certificate, etc.
The following instructions show how to set up a simple self-signed CA certificate.
-name:Create private key with password protection
@@ -193,7 +193,7 @@
In the following example, we assume that the certificate to sign (including its private key) are on server_1, while our CA certificate is on server_2. We do not want any key material to leave each respective server.
-name:Create private key for new certificate on server_1
diff --git a/branch/main/docsite/guide_selfsigned.html b/branch/main/docsite/guide_selfsigned.html
index ae329658..cd0e2000 100644
--- a/branch/main/docsite/guide_selfsigned.html
+++ b/branch/main/docsite/guide_selfsigned.html
@@ -14,11 +14,11 @@
-
-
-
-
-
+
+
+
+
+
@@ -152,7 +152,7 @@
The community.crypto collection offers multiple modules that create private keys, certificate signing requests, and certificates. This guide shows how to create self-signed certificates.
For creating any kind of certificate, you always have to start with a private key. You can use the community.crypto.openssl_privatekey module to create a private key. If you only specify path, the default parameters will be used. This will result in a 4096 bit RSA private key:
-name:Request a new certificate from Entrust with bare minimum parameters.Will request a new certificate if current one is valid but within 30days of expiry. If replacing an existing file in path, will back it up.
@@ -959,7 +959,7 @@ see
-
-name:Request domain validation using email validation for client ID of 2.community.crypto.ecs_domain:domain_name:ansible.com
@@ -401,7 +401,7 @@ see
-
The following index documents all environment variables declared by plugins in collections.
Environment variables used by the ansible-core configuration are documented in Ansible Configuration Settings.