On 1/16/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
Sorry this has taken a while to look at - hopefully I'm not too late
to make a meaningful contribution...
Not a problem. I still haven't finished a patch yet and am certainly
still open to suggestions.
I would make another suggestio
Sorry this has taken a while to look at - hopefully I'm not too late
to make a meaningful contribution...
On 1/12/07, James Bennett <[EMAIL PROTECTED]> wrote:
Other than the fact that it's currently a tuple, is there any reason
not to change this to a dictionary? That'd feel cleaner and make it
On Jan 16, 6:42 pm, Scott Paul Robertson <[EMAIL PROTECTED]> wrote:
I use LDAP a bit differently. Using the LDAPBackend in ticket #2507
works rather well for me. When I wrote the patch, I understood that to
use the current auth system means to make User objects. I for one was
happy with this bec
On Tue, Jan 16, 2007 at 09:49:51AM -, PoBK wrote:
> I'm not certain how anyone else feels about this, but personally, I
> hate the fact that I have to have a DB for authorization if using the
> contributed auth module. AAA should be one entity since it breaks the
> whole loosely decoupled DRY p
On Jan 11, 11:36 pm, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
* The real thing we've been discussing, though, is a way for apps to get ahold
of users after they've been created by a third-party authenticator. For
example, on my sites I'm gonna want everyone to have a username whether they
u
I like the ideas Joseph.
While we are naming backends, let's also use the backend name to key
the backend information in the session data (see [1]) so that different
backends can be used for different areas of your site.
Maybe something like the value of session['_auth_user_backend']
becoming a
On 1/11/07, Nicola Larosa (tekNico) <[EMAIL PROTECTED]> wrote:
>
> Every middle-to-big project has its own version, and Django is no
> exception, look in django.utils.datastructures.
I have a patch ready to go for named backends, and it uses
django.utils.datastructures.SortedDict from django pure
Howdy all --
Joseph and I have been discussing this IRL over that past couple of days, but
I probably should summarize what we've been talking about.
Mostly I love this stuff, but I'll skip the glowing praise () and pick a
nit or two:
* I always hate doing schema changes to built-in apps; add
Jacob Kaplan-Moss wrote:
> * The real thing we've been discussing, though, is a way for apps to get ahold
> of users after they've been created by a third-party authenticator. For
> example, on my sites I'm gonna want everyone to have a username whether they
> use OpenID, LDAP, or whatever.
>
>
On 11 Gen, 22:34, "Joseph Kocherhans" <[EMAIL PROTECTED]> wrote:
> I'd love to use a dictionary, but the order of backends matters. I
> wish python had a decent syntax for what basically amounts to an
> ordered dict.
It's a FAQ, and bait for flamefests, here's a big one:
http://groups-beta.googl
On 1/11/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 1/10/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> > I propose to register and lookup backends by name to fix this
> > problem. Here's a configuration sample:
> >
> > # a tuple of (name, path) tuples
> > AUTHENTICATION_BACKEN
On 1/10/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> I propose to register and lookup backends by name to fix this
> problem. Here's a configuration sample:
>
> # a tuple of (name, path) tuples
> AUTHENTICATION_BACKENDS = (
> ('default', 'django.contrib.auth.backends.ModelBac
On Wed, Jan 10, 2007 at 01:10:03PM -0600, Joseph Kocherhans wrote:
>
> 1. Named auth backends
>
> Right now, user logins are coupled to the actual location of an auth
> backend. The python dotted path of the backend is stored in the user's
> session when they login. If you were to move the backen
1. Named auth backends
Right now, user logins are coupled to the actual location of an auth
backend. The python dotted path of the backend is stored in the user's
session when they login. If you were to move the backend to a
different module, any user who was logged in via that backend would
get
14 matches
Mail list logo
