6

I am using Deadbolt 2 with Playframework 2.1.

In the getSubject() function of my DeadboltHandler I check the user password and retrieve the user from the database.

Is it possible to access this user in my controllers to avoid retrieving the user twice per request?

toro2k
  • 19,020
  • 7
  • 64
  • 71
user2440437
  • 121
  • 1
  • 6

1 Answers1

3

Steve, the developer of Deadbolt, suggested me the following:

the trick is to store the user in the context, and then have your controller or deadbolt handler to access it. This allows you to store the user by the actual class, and not have to use getSubject() and cast the resulting Subject to your actual User class.

So I decided to save the User object in the args-Field of Http.Context.current() and it works like a charm!

user2440437
  • 121
  • 1
  • 6
  • I'll make sure this is documented in the user guide : https://github.com/schaloner/deadbolt-2-guide – Steve Chaloner Jun 04 '13 at 07:10
  • @SteveChaloner: is this already documented? I couldn't find it. And I don't understand how storing the user in the http context avoids casting? After all it is a simple (string -> object) map, so I must cast it to my concrete class, if I want to use it. – knittl May 30 '14 at 12:00
  • 3
    @SteveChaloner and what about Scala? There is no `Http.Context` – HEX Jun 28 '14 at 11:27