-
Notifications
You must be signed in to change notification settings - Fork 2
On this page you should find answers to the most common questions - if you feel there is something missing just drop me a note.
There are two built-in accounts which you can use. Either the John Doe who has administrator privileges or Jane Doe who only has customer privileges. For John use the login [email protected] and password password. For Jane you can use [email protected] and also the password password.
We are using Deadbolt to check whether a Subject is present and then proceed with using CurrentAccount to get that subject (aka. the currently authenticated user).
This might cause trouble since we are using Deadbolt annotations on some controller actions,
while CurrentAccount is defined on the controller class.
Play invokes action-level annotations prior invoking the controller-level actions.
Thus, the time Deadbolt tries to check whether a user is logged in it never finds one because our action hasn't run at that time.
Hence Deadbolt authorizations never succeed.
To circumvent this, we tell Deadbolt to defer execution until the DeferredDeadbolt annotation is executed - which we placed after the CurrentAccount action.