Cherry-pick #19900 to 7.x: [Elastic Agent] Require --insecure on enroll for connection to Kibana #19910
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
botelastic
bot
added
the
needs_team
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
botelastic
bot
removed
the
needs_team
|
backport LGTM |
ph
approved these changes
Jul 14, 2020
|
@blakerouse I think this PR is missing a few commits the failures are related? |
…elastic#19900) * Add insecure option to enroll. * Set TLS to not verify on --insecure. * Run mage fmt * Add changelog. * Update enroll for certificate-authorities and ca-sha256. * Update changelog. * Update docstring. (cherry picked from commit 55c4534)
blakerouse
force-pushed
the
backport_19900_7.x
branch
from
92dd977 to
0876631
Compare
2 tasks
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.
Cherry-pick of PR #19900 to 7.x branch. Original message:
What does this PR do?
Adds a
--insecureoption toenrollcommand to allow enrollment to Kibana with SSL that is insecure. Adds the requirement of using--insecurewhen using the HTTP protocol.This also includes a rename of
--ca_sha256to--ca-sha256and--certificate_authoritiesto--certificate-authorities. From a command line standpoint I think its best to standardize on-versus a mix of-and_.Why is it important?
To strongly require users to use secure connection to Kibana.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Related issues