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

Consider introducing a new authorization rules model #13277

Open
jgrandja opened this issue Jun 5, 2023 · 1 comment
Open

Consider introducing a new authorization rules model #13277

jgrandja opened this issue Jun 5, 2023 · 1 comment
Labels
theme: partner-use-cases Use cases we identified with a partner (an established contributor) type: enhancement A general enhancement

Comments

@jgrandja
Copy link
Contributor

jgrandja commented Jun 5, 2023

We should consider introducing a new authorization rules model.

Defining the authorization rules should be simple and natural and more importantly should work with any "secured resource". The "secured resource" could be any of the following: a web endpoint, an object instance, a method on an object instance, a group of object instances, etc.

We should also ensure that other 3rd party authorization libraries/frameworks can be plugged-in as extension implementations.

Related gh-13266

@jgrandja jgrandja added the type: enhancement A general enhancement label Jun 5, 2023
@rwinch
Copy link
Member

rwinch commented Jun 12, 2023

It might be useful for you to provide an example of where the current authorization is not working and what it might look like from a users perspective.

@sjohnr sjohnr added the theme: partner-use-cases Use cases we identified with a partner (an established contributor) label Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme: partner-use-cases Use cases we identified with a partner (an established contributor) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

3 participants