Open 030 opened 7 years ago
check out the PlayAuthenticate usage sample, it uses deadbolt for authorisation.
On 6/22/17, 030 notifications@github.com wrote:
Authentication works, but does this project also support authorization? E.g. userA could authenticate, but is not authorized to view this page, while userB is.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/joscha/play-authenticate/issues/340
Shall I create a PR if the deadbolt works as the related README section seems to be empty https://github.com/joscha/play-authenticate/blob/master/samples/java/Getting%20Started.md#using-deadbolt
Sounds good to me. @joscha ??
On 6/22/17, 030 notifications@github.com wrote:
Shall I create PR if the deadbolt works as the related README section seems to be empty https://github.com/joscha/play-authenticate/blob/master/samples/java/Getting%20Started.md#using-deadbolt
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/joscha/play-authenticate/issues/340#issuecomment-310444406
@030 sure, have a look at the sample app, deadbolt is in there - the Getting started guide is quite outdated, any updates are highly appreciated.
Thanks for your support @oexza!
@oexza and @joscha I have read the deadbolt documentation and checked the sample code, made some changes to understand it more and tried to explain how one could prevent that users could see certain content by pasting an example from the sample app. Could you review the PR?
Authentication works, but does this project also support authorization? E.g. userA could authenticate, but is not authorized to view this page, while userB is allowed.