Authorized Route Migration for routes owned by @elastic/kibana-security #4
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.
Authz API migration for authorized routes
This PR migrates
access:<privilege>
tags used in route definitions to new security configuration.Please refer to the documentation for more information: Authorization API
Before Migration:
Access control tags were defined in the
options
object of the route:After Migration:
Tags have been replaced with the more robust
security.authz.requiredPrivileges
field undersecurity
:What to do next?
access
tags.Any questions?
If you have any questions or need help with API authorization, please reach out to the
@elastic/kibana-security
team.