On Sep 16, 1:55 pm, Chris Babcock <[email protected]> wrote:
> 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.
There are few reasons I want to maintain two distinct auth systems,
and you've already mentioned two. Following are a couple of additional
reasons:
1. Separating admin and users into two distinct tables simplifies
management of each respective group.
2. Users' table would not have fields like is_staff and is_superuser
thus completely eliminating the possibility of user's 'accidentally'
gaining admin/staff rights.
Rather than sub-classing the auth models and re-working them to fit my
needs, would it be easier to create my own 'simple' auth models/views?
For the users, I only need to check the username/password pair and
then instantiate a session.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
