[Security] Moved reset_creds call to reset_internal_creds#176410
Merged
[Security] Moved reset_creds call to reset_internal_creds#176410
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
fb4c1ed to
f35fad0
Compare
Contributor
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
MadameSheema
approved these changes
Feb 9, 2024
Contributor
MadameSheema
left a comment
There was a problem hiding this comment.
LGTM!!! Thanks!! :)
jbudz
approved these changes
Feb 9, 2024
semd
approved these changes
Feb 9, 2024
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @dkirchan |
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this pull request
Feb 15, 2024
…6410) ## Summary Actions needed following the email that was sent about the breaking change : > API: rather than returning credentials for a privileged "elastic" user, [we'll return](https://elasticco.atlassian.net/browse/CP-5477) credentials for a much-less privileged "admin" user. Note this is the user that can be manipulated by customers. This new user won't be an "operator" user anymore: any test that relies on this user being able to do things such as retrieving the cluster health, role mappings, node stats, etc. would therefore break. > A second set of credentials can be retrieved for a privileged "testing-internal" user through a dedicated API endpoint. To retrieve credentials for that user, please update your automation with a small change: > 1. rather than calling the _reset-credentials endpoint, please call the[_reset-internal-credentials > 2. remove any hard-coded reference of the "elastic" user: the new username is returned in the API response --------- Co-authored-by: Gloria Hornero <gloria.hornero@elastic.co>
fkanout
pushed a commit
to fkanout/kibana
that referenced
this pull request
Mar 4, 2024
…6410) ## Summary Actions needed following the email that was sent about the breaking change : > API: rather than returning credentials for a privileged "elastic" user, [we'll return](https://elasticco.atlassian.net/browse/CP-5477) credentials for a much-less privileged "admin" user. Note this is the user that can be manipulated by customers. This new user won't be an "operator" user anymore: any test that relies on this user being able to do things such as retrieving the cluster health, role mappings, node stats, etc. would therefore break. > A second set of credentials can be retrieved for a privileged "testing-internal" user through a dedicated API endpoint. To retrieve credentials for that user, please update your automation with a small change: > 1. rather than calling the _reset-credentials endpoint, please call the[_reset-internal-credentials > 2. remove any hard-coded reference of the "elastic" user: the new username is returned in the API response --------- Co-authored-by: Gloria Hornero <gloria.hornero@elastic.co>
4 tasks
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.
Summary
Actions needed following the email that was sent about the breaking change :