I am trying to write an application that allows two different kinds of authentication: Users in the wild can register and use the site with a new username, password and email and authenticate as usual, and others can use a single-sign-on solution provided by my university. django- cas (http://code.google.com/p/django-cas/) and django-cas-provider (http://nitron.org/projects/django-cas-provider/) both handle the single-sign-on solution, but they overload the username field to correspond to the username provided by CAS. This means that if someone registers as "johndoe" then someone who authenticates as "johndoe" with CAS will suddenly have access to the internals of the other account.
Is there a way to separate out these authentication methods so that both can be used on the same django installation? (They both need access to the same database of information.) If this isn't possible, I may try to create a whole second instance of django running on the same database (but then they both will want to use the "auth_users" table anyways). -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
