Instructions to retrieve keystore pwd #84340
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In 8.0.0. we introduce TLS autoconfiguration. We store the key and certificate materials in password protected PKCS#12 keystores and we store these passwords in the elasticsearch keystore. This commit adds instructions on how to get hold of the passwords for users to inspect or alter the PKCS#12 keystores.
jkakavas
added
>docs
elasticmachine
added
Team:Docs
|
Pinging @elastic/es-security (Team:Security) |
|
Pinging @elastic/es-docs (Team:Docs) |
jrodewig
approved these changes
Feb 24, 2022
jrodewig
reviewed
Feb 24, 2022
Comment on lines
25
to
35
| Use the following command to retrieve the password for `transport.p12`: | ||
| [source,sh] | ||
| ------------------------- | ||
| bin/elasticsearch-keystore show xpack.security.transport.ssl.keystore.secure_password | ||
| ------------------------- | ||
|
|
||
| Use the following command to retrieve the password for `http.p12`: | ||
| [source,sh] | ||
| ------------------------- | ||
| bin/elasticsearch-keystore show xpack.security.http.ssl.keystore.secure_password | ||
| ------------------------- |
There was a problem hiding this comment.
Should we flip the order of these snippets so they match the order above?
There was a problem hiding this comment.
On mobile but I’ll make the change later, makes sense!
Co-authored-by: James Rodewig <[email protected]>
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Mar 14, 2022
In 8.0.0. we introduce TLS autoconfiguration. We store the key and certificate materials in password protected PKCS#12 keystores and we store these passwords in the elasticsearch keystore. This commit adds instructions on how to get hold of the passwords for users to inspect or alter the PKCS#12 keystores. (cherry picked from commit 8cebba5)
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Mar 14, 2022
In 8.0.0. we introduce TLS autoconfiguration. We store the key and certificate materials in password protected PKCS#12 keystores and we store these passwords in the elasticsearch keystore. This commit adds instructions on how to get hold of the passwords for users to inspect or alter the PKCS#12 keystores. (cherry picked from commit 8cebba5)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Mar 14, 2022
In elastic#84340 we adjusted the docs to show instructions on how to retrieve TLS keystores passwords from the elasticsearch keystore but the security-files-reference.asciidoc was not referenced in all places where the instructions should be used. This commit changes that and also removes references for beta versions.
jkakavas
added a commit
that referenced
this pull request
Mar 15, 2022
In #84340 we adjusted the docs to show instructions on how to retrieve TLS keystores passwords from the elasticsearch keystore but the security-files-reference.asciidoc was not referenced in all places where the instructions should be used. This commit changes that and also removes references for beta versions.
jkakavas
added a commit
that referenced
this pull request
Mar 15, 2022
In 8.0.0. we introduce TLS autoconfiguration. We store the key and certificate materials in password protected PKCS#12 keystores and we store these passwords in the elasticsearch keystore. This commit adds instructions on how to get hold of the passwords for users to inspect or alter the PKCS#12 keystores. (cherry picked from commit 8cebba5)
jkakavas
added a commit
that referenced
this pull request
Mar 15, 2022
In 8.0.0. we introduce TLS autoconfiguration. We store the key and certificate materials in password protected PKCS#12 keystores and we store these passwords in the elasticsearch keystore. This commit adds instructions on how to get hold of the passwords for users to inspect or alter the PKCS#12 keystores. (cherry picked from commit 8cebba5)
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Mar 15, 2022
In elastic#84340 we adjusted the docs to show instructions on how to retrieve TLS keystores passwords from the elasticsearch keystore but the security-files-reference.asciidoc was not referenced in all places where the instructions should be used. This commit changes that and also removes references for beta versions. (cherry picked from commit 7c33a77)
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Mar 15, 2022
In elastic#84340 we adjusted the docs to show instructions on how to retrieve TLS keystores passwords from the elasticsearch keystore but the security-files-reference.asciidoc was not referenced in all places where the instructions should be used. This commit changes that and also removes references for beta versions. (cherry picked from commit 7c33a77)
jkakavas
added a commit
that referenced
this pull request
Mar 15, 2022
In #84340 we adjusted the docs to show instructions on how to retrieve TLS keystores passwords from the elasticsearch keystore but the security-files-reference.asciidoc was not referenced in all places where the instructions should be used. This commit changes that and also removes references for beta versions. (cherry picked from commit 7c33a77)
jkakavas
added a commit
that referenced
this pull request
Mar 15, 2022
In #84340 we adjusted the docs to show instructions on how to retrieve TLS keystores passwords from the elasticsearch keystore but the security-files-reference.asciidoc was not referenced in all places where the instructions should be used. This commit changes that and also removes references for beta versions. (cherry picked from commit 7c33a77)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In 8.0.0. we introduce TLS autoconfiguration. We store the key and
certificate materials in password protected PKCS#12 keystores and
we store these passwords in the elasticsearch keystore.
This commit adds instructions on how to get hold of the passwords
for users to inspect or alter the PKCS#12 keystores.