From 14d4a4fc3b039324bdc30fab4953d9e57651b49c Mon Sep 17 00:00:00 2001 From: Chris Adams Date: Fri, 1 Mar 2019 01:26:00 -0500 Subject: [PATCH] docs: SAN prefixes are required for openssl_csr (#53144) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The openssl_csr docs use “should” where (at least following IETF nomenclature) “must” would be more accurate. See #53141 +label: docsite_pr --- lib/ansible/modules/crypto/openssl_csr.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/ansible/modules/crypto/openssl_csr.py b/lib/ansible/modules/crypto/openssl_csr.py index 147cdc8856..ab3cdcba37 100644 --- a/lib/ansible/modules/crypto/openssl_csr.py +++ b/lib/ansible/modules/crypto/openssl_csr.py @@ -107,7 +107,7 @@ options: description: - SAN extension to attach to the certificate signing request. - This can either be a 'comma separated string' or a YAML list. - - Values should be prefixed by their options. (i.e., C(email), C(URI), C(DNS), C(RID), C(IP), C(dirName), + - Values must be prefixed by their options. (i.e., C(email), C(URI), C(DNS), C(RID), C(IP), C(dirName), C(otherName) and the ones specific to your CA) - Note that if no SAN is specified, but a common name, the common name will be added as a SAN except if C(useCommonNameForSAN) is