TurboGears allows you define you own classes to use with the Identity management system. You can set in that up in <yourapp>/config/app.cfg.
They are defined in these three lines. # identity.soprovider.model.user="cogforum.model.User" # identity.soprovider.model.group="cogforum.model.Group" # identity.soprovider.model.permission="cogforum.model.Permission" Of course your must provide the right kind of interface. The only place that I could find figure this out is the source code: http://trac.turbogears.org/turbogears/browser/trunk/turbogears/identity/soprovider.py . That is the link to the latest version of the file in svn. The TG_User, TG_Group and TG_Permission classes are located there. As long as you define the same attributes and methods everything should work. You can then hook up what ever back end you want to that your classes. Note: For TG_User and TG_Group the displayname attributes and emailAddress for TG_User might not be needed (at least they aren't used in the rest of soprovider.py). So you shouldn't have to put those columns in your database if you don't need them. I kind of think that at least the emailAddress shouldn't be there, if not the displaynames too. Here is blog entry about TurboGears and SQLAlchemy that you might not of seen: http://nerd.newburyportion.com/2006/02/turbogears-is-now-unstoppable , it should help with getting it to work with TurboGears. It is important to note that cool tools like Catwalk won't work with SQLAlchemy because they were designed around SQLObject. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
