-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Fix enrollment api key role descriptor application name #122798
[Fleet] Fix enrollment api key role descriptor application name #122798
Conversation
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: cc @nchaulet |
Pinging @elastic/fleet (Team:Fleet) |
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.
Small enough fix to just approve outright. Thanks for the quick turn around here 🚀
(cherry picked from commit c180aac)
(cherry picked from commit c180aac)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit c180aac) Co-authored-by: Nicolas Chaulet <[email protected]>
(cherry picked from commit c180aac) Co-authored-by: Nicolas Chaulet <[email protected]>
@nchaulet Glad to see we also got this into 7.x. This removes a potential problem where an older version of Kibana is talking to a newer version of Elasticsearch. |
Summary
Resolve elastic/beats#29811
In elastic/elasticsearch#82049 Elasticsearch started to validate the role descriptor inside an API key our application name was invalid so it started to throw and block the creation of enrollment API key.
That PR fix that by providing a valid application name.