-
Notifications
You must be signed in to change notification settings - Fork 186
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
No support for authorization in service provider #188
Comments
Thanks for the contribution! |
Hey - wait what happened? Did you already merge it in? I was working on a demo and documentation per your request :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is created as something to refer to for pull request: #174
Once the authenticaiton provider(e.g the Active Directory) has authenticated the principal, waffle
currently assumes that the principal is authorized to use the service that the service provider(e.g service/application) that is using waffle to authenticate towards AD. This may not be the case. The principal may very well be in the Active Directory but not be authorized to use the service that the current service provider provides.
The text was updated successfully, but these errors were encountered: