Hi Lee, What you're asking for sounds like a perfectly reasonable use case. I haven't had a chance to dive into identity yet myself, so I'll have to think about this another time. But, I'd suggest opening a ticket with your use case in it, because a solution *should* exist to the problem, even if it doesn't now.
Kevin On 12/9/05, Lee McFadden <[EMAIL PROTECTED]> wrote: > > No, we're still not getting there. I don't want to test for > groups/users from both models. I don't want the two parts of the app > to know anything about the other's authentication. > > What I'm getting at is this: > > Is it possible to have two *completely descreet* identity providers > for different controllers (or different apps if I want to mount more > than one app in one cherrypy server). Neither controller knows or > cares about the other's authentication. > > What would be nice is if you could change identity provider in a > similar fashion to the way you protect a whole controller. > > As it is, I'm bored of trying to bend the current provider to my will > and I'll impliment my own simple authentication for the client side. > > Lee > > On 09 Dec 2005 10:23:23 -0200, Jorge Godoy <[EMAIL PROTECTED]> wrote: > > > > Lee McFadden <[EMAIL PROTECTED]> writes: > > > > > As it stands it seems that this isn't possible without having two > > > seperate apps and a front end to proxy the app depending on which > > > section you're going to. Or am I mistaken? > > > > How about using the default identity manager for visitors and "creating your > > own identity model" > > (http://nerd.newburyportion.com/2005/11/creating-your-own-identity-model) > > for > > LDAP users? > > > > Then you could say something like: > > > > ================================================================================ > > from turbogears import identity > > from custom import custom_identity > > > > if 'admin' in custom_identity.current.ldap_groups: > > <is an admin> > > elif 'visitor' in identity.current.groups: > > <is a visitor> > > ================================================================================ > > > > But I'm just guessing here. I've never done that -- yet. > > > > It looks a "little" more complex but tying it with LDAP isn't all that hard > > (at least, codes where I used Python + LDAP weren't hard to write). > > > > -- > > Jorge Godoy <[EMAIL PROTECTED]> > > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
