20.03.2012 20:40, william ratcliff ?????: > To facilitate these different cases, can we have a pluggable > "Authentication Service" where the user provides a "credential" which > then returns a result of whether the credential is valid or not? We > could then implement a few "standard" authentication plugins, such as > username/password, email address/password. Third party apps would > run against the authentication service, so they shouldn't depend on a > particular implementation of user in the database. For legacy > users, the current username/password could be implemented and run as > the default , so they only have to migrate if they want to...The > settings file could be used to register authentication "providers" > (for example EmailAuth or UsernameAuth) with the authentication > service. If there are multiple authentication methods (users can sign > in via openauth or email address for example), then they would > fallover in the order they are registered with the authentication > service (using settings.py might require some effort to preserve order > and avoid multiple registrations...).
But django has a auth backend or you mean something else. https://docs.djangoproject.com/en/dev/topics/auth/#specifying-authentication-backends I think that task of identity is completely task of auth backend. <https://docs.djangoproject.com/en/dev/topics/auth/#other-authentication-sources> -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
