refactor(api keys): Display personal API keys as default view#245261
Merged
SiddharthMantri merged 2 commits intoelastic:mainfrom Dec 5, 2025
Merged
refactor(api keys): Display personal API keys as default view#245261SiddharthMantri merged 2 commits intoelastic:mainfrom
SiddharthMantri merged 2 commits intoelastic:mainfrom
Conversation
SiddharthMantri
added
release_note:enhancement
Team:Security
Contributor
|
Pinging @elastic/kibana-security (Team:Security) |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
|
jeramysoucy
approved these changes
Dec 5, 2025
Contributor
jeramysoucy
left a comment
jeramysoucy
left a comment
There was a problem hiding this comment.
LGTM! I also tested locally in a serverless configuration, where I needed to add a managed key to see the filters, but worked as expected.
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 5, 2025
…c#245261) Closes elastic#245255 ## Summary Changes the default display view of the API Keys page to show Personal keys only. ### Release note API Keys management page now defaults to showing personal API Keys only ### How to test - Start ES and Kibana - Navigate to Stack Management -> API Keys - Create a few different types of Keys: Personal, Cross Cluster - Create a Managed key by setting the metadata to ``` { "managed": true } ``` - Now when reloading the page, the default view should only show the Personal keys and the Personal filter tab should be selected. ### Screenshots - On Main <img width="1716" height="1284" alt="Screenshot 2025-12-04 at 15 49 35" src="https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda" /> - On this PR <img width="1718" height="1287" alt="Screenshot 2025-12-04 at 15 50 06" src="https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e" /> If no personal keys are present, but managed/cross cluster are then the view defaults to showing no keys and the filter still enabled <img width="1471" height="584" alt="image" src="https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 0dd1c86)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 5, 2025
…c#245261) Closes elastic#245255 ## Summary Changes the default display view of the API Keys page to show Personal keys only. ### Release note API Keys management page now defaults to showing personal API Keys only ### How to test - Start ES and Kibana - Navigate to Stack Management -> API Keys - Create a few different types of Keys: Personal, Cross Cluster - Create a Managed key by setting the metadata to ``` { "managed": true } ``` - Now when reloading the page, the default view should only show the Personal keys and the Personal filter tab should be selected. ### Screenshots - On Main <img width="1716" height="1284" alt="Screenshot 2025-12-04 at 15 49 35" src="https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda" /> - On this PR <img width="1718" height="1287" alt="Screenshot 2025-12-04 at 15 50 06" src="https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e" /> If no personal keys are present, but managed/cross cluster are then the view defaults to showing no keys and the filter still enabled <img width="1471" height="584" alt="image" src="https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 0dd1c86)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 5, 2025
…c#245261) Closes elastic#245255 ## Summary Changes the default display view of the API Keys page to show Personal keys only. ### Release note API Keys management page now defaults to showing personal API Keys only ### How to test - Start ES and Kibana - Navigate to Stack Management -> API Keys - Create a few different types of Keys: Personal, Cross Cluster - Create a Managed key by setting the metadata to ``` { "managed": true } ``` - Now when reloading the page, the default view should only show the Personal keys and the Personal filter tab should be selected. ### Screenshots - On Main <img width="1716" height="1284" alt="Screenshot 2025-12-04 at 15 49 35" src="https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda" /> - On this PR <img width="1718" height="1287" alt="Screenshot 2025-12-04 at 15 50 06" src="https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e" /> If no personal keys are present, but managed/cross cluster are then the view defaults to showing no keys and the filter still enabled <img width="1471" height="584" alt="image" src="https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 0dd1c86)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Dec 5, 2025
…245261) (#245451) # Backport This will backport the following commits from `main` to `9.1`: - [refactor(api keys): Display personal API keys as default view (#245261)](#245261) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-12-05T22:00:13Z","message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Security","Feature:Users/Roles/API Keys","backport:all-open","v9.3.0"],"title":"refactor(api keys): Display personal API keys as default view","number":245261,"url":"https://github.com/elastic/kibana/pull/245261","mergeCommit":{"message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245261","number":245261,"mergeCommit":{"message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b"}}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com>
kibanamachine
added a commit
that referenced
this pull request
Dec 5, 2025
…245261) (#245450) # Backport This will backport the following commits from `main` to `8.19`: - [refactor(api keys): Display personal API keys as default view (#245261)](#245261) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-12-05T22:00:13Z","message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Security","Feature:Users/Roles/API Keys","backport:all-open","v9.3.0"],"title":"refactor(api keys): Display personal API keys as default view","number":245261,"url":"https://github.com/elastic/kibana/pull/245261","mergeCommit":{"message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245261","number":245261,"mergeCommit":{"message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b"}}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com>
kibanamachine
added a commit
that referenced
this pull request
Dec 6, 2025
…245261) (#245452) # Backport This will backport the following commits from `main` to `9.2`: - [refactor(api keys): Display personal API keys as default view (#245261)](#245261) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-12-05T22:00:13Z","message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Security","Feature:Users/Roles/API Keys","backport:all-open","v9.3.0"],"title":"refactor(api keys): Display personal API keys as default view","number":245261,"url":"https://github.com/elastic/kibana/pull/245261","mergeCommit":{"message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245261","number":245261,"mergeCommit":{"message":"refactor(api keys): Display personal API keys as default view (#245261)\n\nCloses https://github.com/elastic/kibana/issues/245255\n\n## Summary\n\nChanges the default display view of the API Keys page to show Personal\nkeys only.\n\n### Release note\nAPI Keys management page now defaults to showing personal API Keys only\n\n\n### How to test\n- Start ES and Kibana\n- Navigate to Stack Management -> API Keys\n- Create a few different types of Keys: Personal, Cross Cluster \n- Create a Managed key by setting the metadata to \n```\n{\n \"managed\": true\n}\n```\n- Now when reloading the page, the default view should only show the\nPersonal keys and the Personal filter tab should be selected.\n\n\n### Screenshots\n\n- On Main\n<img width=\"1716\" height=\"1284\" alt=\"Screenshot 2025-12-04 at 15 49 35\"\nsrc=\"https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda\"\n/>\n\n- On this PR\n<img width=\"1718\" height=\"1287\" alt=\"Screenshot 2025-12-04 at 15 50 06\"\nsrc=\"https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e\"\n/>\n\n\nIf no personal keys are present, but managed/cross cluster are then the\nview defaults to showing no keys and the filter still enabled\n\n<img width=\"1471\" height=\"584\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"0dd1c86557ebc1b62821cac0f462c963b511b73b"}}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com>
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
…c#245261) Closes elastic#245255 ## Summary Changes the default display view of the API Keys page to show Personal keys only. ### Release note API Keys management page now defaults to showing personal API Keys only ### How to test - Start ES and Kibana - Navigate to Stack Management -> API Keys - Create a few different types of Keys: Personal, Cross Cluster - Create a Managed key by setting the metadata to ``` { "managed": true } ``` - Now when reloading the page, the default view should only show the Personal keys and the Personal filter tab should be selected. ### Screenshots - On Main <img width="1716" height="1284" alt="Screenshot 2025-12-04 at 15 49 35" src="https://github.com/user-attachments/assets/c693eab0-3e5a-4292-9895-9cb86b008dda" /> - On this PR <img width="1718" height="1287" alt="Screenshot 2025-12-04 at 15 50 06" src="https://github.com/user-attachments/assets/e0606424-fda8-42e4-b735-6fb7cfa5be8e" /> If no personal keys are present, but managed/cross cluster are then the view defaults to showing no keys and the filter still enabled <img width="1471" height="584" alt="image" src="https://github.com/user-attachments/assets/cdcdba01-0ebe-4309-bb78-b001a6c72b3f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
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
4 participants
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.
Closes #245255
Summary
Changes the default display view of the API Keys page to show Personal keys only.
Release note
API Keys management page now defaults to showing personal API Keys only
How to test
Screenshots
If no personal keys are present, but managed/cross cluster are then the view defaults to showing no keys and the filter still enabled
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.