I'm looking for direction on the best pattern for implementing basic authentication and authorization in Lift. For example, if I already have a Role mapper to store roles in the database, to what do I attach the Role trait in the net.liftweb.http.auth package?
1) The mapper. You would have to make sure there were no naming conflicts ( i.e., def name in the trait and the mapped string, name, in the mapper. Not the best design pattern to link the two, in my humble opinion.) or 2) A new class, or perhaps an object, with the trait that wraps a Role mapper instance. The other piece to the puzzle is managing the list of AuthRoles, create protected resources and build the Lift.authentication cases. If you limit this to Boot, then you give up on dynamic authentication and authorization, or do you? Glenn... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
