Skip to content
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

[8.12] Ensure all API Keys have a defined name (#175721) #175730

Merged
merged 3 commits into from
Jan 27, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.12:

Questions ?

Please refer to the Backport tool documentation

## Summary

Resolves elastic#173890.

API Keys created in the 7.x era did not require a `name`
(https://www.elastic.co/guide/en/elasticsearch/reference/7.5/security-api-create-api-key.html#security-api-create-api-key-request-body).
The `name` is no longer an optional field, but our UIs have come to
assume that a `name` will always be available. This updates our `GET
/internal/security/api_key` API to ensure that a `name` will always
exist.

(cherry picked from commit 707b423)
@kibanamachine kibanamachine force-pushed the backport/8.12/pr-175721 branch from acc57b4 to 81be5fc Compare January 26, 2024 20:29
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @legrego

@kibanamachine kibanamachine merged commit 42f0a85 into elastic:8.12 Jan 27, 2024
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants