Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
# Backport This will backport the following commits from `main` to `8.12`: - [Ensure all API Keys have a defined name (#175721)](#175721) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Larry Gregory","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-01-26T20:16:06Z","message":"Ensure all API Keys have a defined name (#175721)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/173890.\r\n\r\nAPI Keys created in the 7.x era did not require a `name`\r\n(https://www.elastic.co/guide/en/elasticsearch/reference/7.5/security-api-create-api-key.html#security-api-create-api-key-request-body).\r\nThe `name` is no longer an optional field, but our UIs have come to\r\nassume that a `name` will always be available. This updates our `GET\r\n/internal/security/api_key` API to ensure that a `name` will always\r\nexist.","sha":"707b4233898c18e63896581a61ddf8bfb7f20979","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Users/Roles/API Keys","backport:all-open","v8.13.0"],"title":"Ensure all API Keys have a defined name","number":175721,"url":"https://github.com/elastic/kibana/pull/175721","mergeCommit":{"message":"Ensure all API Keys have a defined name (#175721)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/173890.\r\n\r\nAPI Keys created in the 7.x era did not require a `name`\r\n(https://www.elastic.co/guide/en/elasticsearch/reference/7.5/security-api-create-api-key.html#security-api-create-api-key-request-body).\r\nThe `name` is no longer an optional field, but our UIs have come to\r\nassume that a `name` will always be available. This updates our `GET\r\n/internal/security/api_key` API to ensure that a `name` will always\r\nexist.","sha":"707b4233898c18e63896581a61ddf8bfb7f20979"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/175721","number":175721,"mergeCommit":{"message":"Ensure all API Keys have a defined name (#175721)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/173890.\r\n\r\nAPI Keys created in the 7.x era did not require a `name`\r\n(https://www.elastic.co/guide/en/elasticsearch/reference/7.5/security-api-create-api-key.html#security-api-create-api-key-request-body).\r\nThe `name` is no longer an optional field, but our UIs have come to\r\nassume that a `name` will always be available. This updates our `GET\r\n/internal/security/api_key` API to ensure that a `name` will always\r\nexist.","sha":"707b4233898c18e63896581a61ddf8bfb7f20979"}}]}] BACKPORT--> Co-authored-by: Larry Gregory <[email protected]>
- Loading branch information