[DOCS] Clarifying TLS steps #65326
[DOCS] Clarifying TLS steps #65326
Conversation
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-security (Team:Security) |
| Answer `y` if you want to sign your own certificates, or `n` if you want to | ||
| sign certificates with a central CA. |
There was a problem hiding this comment.
I'm not sure that this terminology would clarify which choice to make - that is, "sign your own certificates" isn't particularly clear, and could mean "I want to do it as part of this process" (which would actually mean you should pick n) or "I handle it myself by sending it to someone in my organisation" (which is y).
I would go with something more like this:
| Answer `y` if you want to sign your own certificates, or `n` if you want to | |
| sign certificates with a central CA. | |
| Answer `y` if you need to have your certificates signed by someone else | |
| (such as an internal security team, or a commercial certificate authority), | |
| or `n` if you want to sign certificates with a CA that you have direct access to. |
It feels a bit wordy though, and "direct access" might not be clear enough.
There was a problem hiding this comment.
@tvernum, I like the distinction that you incorporated. I think we can break these ideas into separate sentences:
Answer
yif a trusted authority, such as in internal security team or a commercial certificate authority, will sign your certificates. Answernif you have access to a trusted CA and will sign your own certificates.
x-pack/docs/en/security/securing-communications/node-certificates.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Tim Vernum <tim@adjective.org>
|
@elasticmachine test this please |
|
@elasticmachine update branch |
…cs/elasticsearch into docs__tls-security-updates
|
@elasticmachine update branch |
|
@elasticmachine test this please |
|
@elasticmachine update branch |
* [DOCS] Clarifying TLS steps * Fix file name * Clarifying note based on reviewer feedback
Provides clarity around which certificates to copy into configuration directories when configuring TLS.
Closes #65245