chore: Remove mentions of username/password for Kibana#25
Merged
Conversation
5 tasks
shashank-elastic
approved these changes
Mar 20, 2025
Mikaayenson
approved these changes
Mar 20, 2025
docs/core_component_syncing_rules_and_data_from_vcs_to_elastic_security.md
Show resolved
Hide resolved
Contributor
|
I don't think this is a blocker for merging this PR, but we should also then update the quick start slides in the End to End Reference page to recommend API auth as well (specifically slide 41) But seeing as we probably want to update these slides to a more recent version anyway, happy to defer to another issue/PR. |
Contributor
|
Added #26 to track above comment 👍 |
eric-forte-elastic
approved these changes
Mar 20, 2025
This file contains hidden or 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
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.
Issue
What was changed
Dropping username/password auth method for Kibana in favour of API key