On Wed, 16 Sep 2009 10:26:15 -0700 (PDT) Dan06 <dan.king...@yahoo.com> wrote:
> Is there a way to have multiple implementations of django's > authentication/authorization system? In my practice blog-type site, > I've implemented django's auth/auth system as is. I'd like to use the > default implementation solely for administrators of the site. For > users of the site, on the other hand, I'd like to have a derivation of > django's auth/auth system - which will have the same functionality as > the default implementation, but have a separate set of user tables and > different fields. > > Anyone know how to do what I've described? Thanks. Is there any particular reason to maintain two distinct authentication databases? You could sub-class the Django auth models and deploy your subclass in parallel, but that is not a trivial deployment task. It would be easier to just authorize the users you want for administrative tasks. The two legitimate use cases I see for wanting truly separate databases for users and administrators would be want admins to be able to function without interacting with users and actually forbidding employees that administer the site from 'wasting time' performing non-administrative functions. Hiding presence information for admins and/or creating an adminstrative class that doesn't have access to site features is better design and likely easier to implement. Chris Babcock
signature.asc
Description: PGP signature
