-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Advanced Auth Features #2000
Comments
Just some real world feedback: A user might be able to "only read data (role: 'reader') from realm A", but also "can be an admin (role: 'admin') in realm B". So I would expect:
In combination with the nested behavior this would allow a user to have read access to all data from company A & C, but also have write privileges to department IV of company A. |
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
Description
Step 5 from #1035 (comment).
Armed with a small application having authentication and authorization constraints in place, let's look at extensibility and what extension points we may need to define to support those use cases.
Few example scenarios to drive our focus:
Ideally, there should be a documentation and/or a blog-post and/or a reference implementation to make it easier for LB4 users to implement similar functionality in their project.
Previous step: #1999
The text was updated successfully, but these errors were encountered: