[Catalyst] Customizing Authentication/Roles

Matt S Trout dbix-class at trout.me.uk
Fri Sep 15 21:22:09 CEST 2006


Christopher H. Laco wrote:
> Matt S Trout wrote:
> [snip]
>   
>> Alternatively, you could point the user and role models at custom ones
>> with an ACCEPT_CONTEXT that applies ->search({ site_id =>
>> $current_site_id }) based on the request.
>>
>>     
>
> That makes sense, but the light isn't on upstairs this morning. :-/
>
> That means I would create my own DB::Role and DB::User, rather than
> letting Catalyst::Model::DBIC::Schema do it for me (Or not use
> DBIC::Schema at all). It would seem the down side of that approach would
> be that I'll already have a User and Role models for the non-Auth
> stuffs. Any ACCEPT_CONTEXT crazyness would mean I would need two models
> for the same Roles and Users; one set for controllers to use, and one
> set just to make Auth happy.
>
> But really, my Users and Roles models wouldn't be raw DBIC model at all,
>  but more likely core modules used outside of Mango to do user/role
> management.
>
> The more I think about it, the more I don't think I want Mango being a
> multiple sites in one instance kind of thing. That's too much complexity
> for the short time frame, and removing that requirement makes things
> much less complicated.
I'd agree with that, then we can have a proper think about how to do 
that once 5.80 is out (since yes, the app/context split is scheduled for 
then)

-- 
     Matt S Trout       Offering custom development, consultancy and support
  Technical Director    contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd.  mst (at) shadowcatsystems.co.uk for more information

+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +




More information about the Catalyst mailing list