On 4/11/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Joseph Kocherhans wrote:
>
> >The authentication api has been simplified into 5 functions in
> >django.contrib.auth.utils
> >
> >authenticate(request)
> >Returns a user if valid credentials were found in the request.
> >
> >login(request, us
Joseph Kocherhans wrote:
>The authentication api has been simplified into 5 functions in
>django.contrib.auth.utils
>
>authenticate(request)
>Returns a user if valid credentials were found in the request.
>
>login(request, user)
>Persist a user id and a backend name in the session. This way a use
There is a new patch available for multiple auth backends.
http://code.djangoproject.com/attachment/ticket/1428/multiauth.diff
Authentication is handled by two lists of plugins. These are defined
by the AUTHENTICATION_BACKENDS and CREDENTIAL_PLUGINS settings. Each
should be a tuple of strings, s
On 3/14/06, Max Battcher <[EMAIL PROTECTED]> wrote:
>
> Joseph Kocherhans wrote:
> > On 3/14/06, Max Battcher <[EMAIL PROTECTED]> wrote:
> >> -1. I don't want to add layer after layer of code to my views to
> >> support whatever authentication backends I feel necessary.
> >
> > You don't have to.
Gary Wilson wrote:
> I think it would be nice to have the authentication backend
> configurable per app instead of project-wide. This way, I could use an
> LDAP backend for the app that my users use, and use the builtin backend
> for the admin app.
I continue to use the example of OpenID authent
I think it would be nice to have the authentication backend
configurable per app instead of project-wide. This way, I could use an
LDAP backend for the app that my users use, and use the builtin backend
for the admin app.
--~--~-~--~~~---~--~~
You received this m
Joseph Kocherhans wrote:
> On 3/14/06, Max Battcher <[EMAIL PROTECTED]> wrote:
>> -1. I don't want to add layer after layer of code to my views to
>> support whatever authentication backends I feel necessary.
>
> You don't have to. There is "one true way" to access authentication
> regardless of
Max Battcher wrote:
> Authentication/Authorization really doesn't belong in every view. That
> way leads to bad coupling and lots of repetition.
please note, that even with the current auth-system, you have to handle
it in every view.
gabor
--~--~-~--~~~---~--~---
On 3/14/06, Max Battcher <[EMAIL PROTECTED]> wrote:
>
> -1. I don't want to add layer after layer of code to my views to
> support whatever authentication backends I feel necessary.
You don't have to. There is "one true way" to access authentication
regardless of the backend. The specific backen
Joseph Kocherhans wrote:
> I've rethought how to implement multiple authentication backends,
> updated the wiki and posted a new patch. This should be a lot simpler
> than the previous attempt. Please check it out, and post your comments
> to the list rather than the wiki. A
I've rethought how to implement multiple authentication backends,
updated the wiki and posted a new patch. This should be a lot simpler
than the previous attempt. Please check it out, and post your comments
to the list rather than the wiki. Also, question for Jacob/Adrian, is
an ldap ba
11 matches
Mail list logo
