-
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
Unauthorized route migration for routes owned by kibana-presentation #198329
Unauthorized route migration for routes owned by kibana-presentation #198329
Conversation
Pinging @elastic/kibana-presentation (Team:Presentation) |
src/plugins/controls/server/options_list/options_list_cluster_settings_route.ts
Outdated
Show resolved
Hide resolved
src/plugins/controls/server/options_list/options_list_suggestions_route.ts
Outdated
Show resolved
Hide resolved
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.
opt-out reasons LGTM! The only one I am slightly concerned about is the options list cluster settings route, but the only piece of config it returns is the allowExpensiveQueries
setting, which is quite unimportant. Additionally, this is tracked in #200779
💚 Build Succeeded
Metrics [docs]
History
|
Starting backport for target branches: 8.x |
…lastic#198329) Migrates unauthorized routes owned by the Presentation team to a new security configuration. (cherry picked from commit 65a75ff)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…ation (#198329) (#205006) # Backport This will backport the following commits from `main` to `8.x`: - [Unauthorized route migration for routes owned by kibana-presentation (#198329)](#198329) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kibana Machine","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-19T20:24:23Z","message":"Unauthorized route migration for routes owned by kibana-presentation (#198329)\n\nMigrates unauthorized routes owned by the Presentation team to a new security configuration.","sha":"65a75ffcb733306cddaf0955e00f6273c9051f73","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","Team:Presentation","release_note:skip","Feature:Security/Authorization","v9.0.0","backport:prev-minor","Authz: API migration"],"title":"Unauthorized route migration for routes owned by kibana-presentation","number":198329,"url":"https://github.com/elastic/kibana/pull/198329","mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-presentation (#198329)\n\nMigrates unauthorized routes owned by the Presentation team to a new security configuration.","sha":"65a75ffcb733306cddaf0955e00f6273c9051f73"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198329","number":198329,"mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-presentation (#198329)\n\nMigrates unauthorized routes owned by the Presentation team to a new security configuration.","sha":"65a75ffcb733306cddaf0955e00f6273c9051f73"}}]}] BACKPORT-->
…lastic#198329) Migrates unauthorized routes owned by the Presentation team to a new security configuration.
…lastic#198329) Migrates unauthorized routes owned by the Presentation team to a new security configuration.
…lastic#198329) Migrates unauthorized routes owned by the Presentation team to a new security configuration.
…lastic#198329) Migrates unauthorized routes owned by the Presentation team to a new security configuration.
Authz API migration for unauthorized routes
This PR migrates unauthorized routes owned by your team to a new security configuration.
Please refer to the documentation for more information: Authorization API
Before migration:
After migration:
What to do next?
Any questions?
If you have any questions or need help with API authorization, please reach out to the
@elastic/kibana-security
team.