New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Invalidate api keys in agents default_api_key_history
on force unenroll
#135910
[Fleet] Invalidate api keys in agents default_api_key_history
on force unenroll
#135910
Conversation
Pinging @elastic/fleet (Team:Fleet) |
54a6891
to
e0d659a
Compare
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
should this be backported as mentioned here? #134029 (comment) |
💚 Build SucceededMetrics [docs]Public APIs missing comments
History
To update your PR or re-run it, just comment with: cc @nchaulet |
yes it probably make sense to backport it |
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
Description
Resolve #134029
On force unenroll we revoke all the api keys of the agents, we were missing keys in
default_api_key_history
that contains api key between config change.That PR solve by revoking these keys if they are present on the agent document.