Re: authentication by email

I'm not a dev that contribute too many directly to Django Project, but aniway I use Django since 0.96, so here is my 2 cents. While Clay's idea have many cool changes and is a really nice idea that should be evaluated I share more Tom's and Daniel's point. Any Django Developer on World that

Re: authentication by email

On Fri, Mar 16, 2012 at 10:05 AM, Carl Meyer wrote: [...] > I am not sure whether this should happen as a separate step or not. In > an ideal world, we would have a longer username field. In the real > world, we have to balance the benefit against the cost, and requiring a >

Re: authentication by email

ses, it takes a --database arg. 4) Add the following release notes: The contrib.auth.models.User model has increased the length of the email field to 254 characters, in order to allow all legal email addresses to be stored. In addition, the email field has been marked as a db index, in order to

Re: authentication by email

Hi Daniel, On 03/15/2012 11:48 AM, Daniel Sokolowski wrote: > The issue here is that django auth is limited, and restrictive and needs > hacks to make it use emails as usernames, we can agree on that yes? Certainly. > We > can also agree that contrib.auth2 with LFK is a complex undertaking far

Re: authentication by email

on't agree that changing the length of the username field is the general solution to the problem of email authentication. First, there's the issue of backwards compatibility: as Carl pointed out, you can't just change the size of the field without requiring a schema migration in every existing django insta

Re: authentication by email

limitation on the username ought to be increased? -Original Message- From: Luke Sneeringer Sent: Thursday, March 15, 2012 2:11 PM To: django-developers@googlegroups.com Subject: Re: authentication by email On March 15, 2012, at 12:23 , Daniel Sokolowski wrote: Carl, I sincerely appreciate

Re: authentication by email

> -Original Message- From: Carl Meyer > Sent: Thursday, March 15, 2012 12:49 PM > To: django-developers@googlegroups.com > Subject: Re: authentication by email > > -- > You received this message because you are subscribed to the Google Groups > "Django developers&

Re: authentication by email

:49 PM To: django-developers@googlegroups.com Subject: Re: authentication by email -- 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 g

Re: authentication by email

On 03/15/2012 09:41 AM, Daniel Sokolowski wrote: > Yes it clearly would, however I see two possible solutions to make it > more friendly: > > 1. We provide MySQL, Sqlite3, PostgreSQL instructions on how to do it - > I mean the actual commands to execute. > 2. Catch the DB error and throw a form

Re: authentication by email

Hi Daniel, On 03/15/2012 09:24 AM, Daniel Sokolowski wrote: > Why can we not just increase the length limit on the username field?, > Why can't we just throw a validation error if data entered is to long > and the schema has not been updated? I think the answer yes we can and > easily. I don't

Re: authentication by email

That would be a workable compromise, yes? -Original Message- From: Daniel Sokolowski Sent: Thursday, March 15, 2012 12:41 PM To: django-developers@googlegroups.com Subject: Re: authentication by email Yes it clearly would, however I see two possible solutions to make it more friendly

Re: authentication by email

Message- From: Luke Sneeringer Sent: Thursday, March 15, 2012 12:28 PM To: django-developers@googlegroups.com Subject: Re: authentication by email On March 15, 2012, at 11:24 , Daniel Sokolowski wrote: Tom makes a good point, but you can already store emails in the username, they are just

Re: authentication by email

atible change than the Django development community has traditionally been comfortable with. Regards, Luke > > -Original Message- From: Tom Evans > Sent: Friday, March 09, 2012 11:46 AM > To: django-developers@googlegroups.com > Subject: Re: authentication by email >

Re: authentication by email

: authentication by email On Fri, Mar 9, 2012 at 3:52 PM, Luke Plant <l.plant...@cantab.net> wrote: On 09/03/12 14:49, Tom Evans wrote: Yes, since no one needs it. Okay no one isn't true, but no one (for true this time) who needed it stepped up and said "I'll implement it and see that it ends

Re: authentication by email

On Thu, Mar 15, 2012 at 22:53, Danny Adair wrote: >[...] > I'd like to see a later, "proper" auth.user that can undo that chaos. I originally thought you intended a setting which let's the user switch from the existing auth to an email auth with corresponding User

Re: authentication by email

On Mon, Mar 12, 2012 at 16:57, Clay McClure wrote: >[...] > New django projects can elect to use an entirely different pluggable auth >[...] > The pluggable-auth-apps fork is barely two days old, so it's still rough > around the edges, and I've almost certainly missed some

Re: authentication by email

On Sun, Mar 11, 2012 at 4:39 AM, Clay McClure wrote: What you are really saying is this: being pragmatic means that we >> prioritise *your* immediate need above the need to keep the code and the >> docs maintainable, and above the need to maintain compatibility with >> existing

Re: authentication by email

ons of the User model noted > above and allows for email authentication. It's still a bit rough around > the edges, but it works, insofar that `manage.py createsuperuser` doesn't > ask for a username, `manage.py changepassword` takes an email address, and > I can login to the admin inte

Re: authentication by email

On 12/03/2012, at 6:58 AM, Joe & Anne Tennies wrote: > I started a new page off the old > https://code.djangoproject.com/wiki/SchemaEvolution > (https://code.djangoproject.com/wiki/SchemaEvolutionDesign). It's not > complete at this point, I just did a brain dump of what I remembered hearing

Re: authentication by email

On 12/03/2012, at 7:08 AM, Joe & Anne Tennies wrote: > Can I ask for one change this late in the project to the 1.4 release if it's > only the documentation for this bug? I'm hoping someone at PyCon might be > able to "sneak this in." > > Can we add a note to the EmailField documentation that

Re: authentication by email

Can I ask for one change this late in the project to the 1.4 release if it's only the documentation for this bug? I'm hoping someone at PyCon might be able to "sneak this in." Can we add a note to the EmailField documentation that states that "The default 75 character max_length is not capable of

Re: authentication by email

I started a new page off the old https://code.djangoproject.com/wiki/SchemaEvolution ( https://code.djangoproject.com/wiki/SchemaEvolutionDesign). It's not complete at this point, I just did a brain dump of what I remembered hearing in the past. Sounds like I'm not TOO far off with my memory.

Re: authentication by email

ted above and > allows for email authentication. It's still a bit rough around the edges, but > it works, insofar that `manage.py createsuperuser` doesn't ask for a > username, `manage.py changepassword` takes an email address, and I can login > to the admin interface with my email addr

Re: authentication by email

icate > by email > True. > - you can write your own login and account creation views > True. > - you can even override admin views by inserting items into > urls.py > True. But these things aren't the problem. It's the auth.User model that poses the challenge. If

Re: authentication by email

On 10/03/2012, at 1:52 AM, Joe & Anne Tennies wrote: > While, I generally agree with the current approach, especially this close to > release. I'm going to play devil's advocate for a bit. > > Schema migrations have been talked about for quite a while. There are at > least 3 external

Re: authentication by email

On 9 March 2012 21:10, Tom Evans wrote: > 2012/3/9 Łukasz Rekucki : >> On 9 March 2012 17:46, Tom Evans wrote: >>> >>> Lets look at one isolated aspect. The User email field in d.c.auth is >>> too short. Emails can be up to

Re: authentication by email

2012/3/9 Łukasz Rekucki : > On 9 March 2012 17:46, Tom Evans wrote: >> >> Lets look at one isolated aspect. The User email field in d.c.auth is >> too short. Emails can be up to 248 characters long, and d.c.auth only >> allows 75. > > The latest

Re: authentication by email

On 9 March 2012 17:46, Tom Evans wrote: > > Lets look at one isolated aspect. The User email field in d.c.auth is > too short. Emails can be up to 248 characters long, and d.c.auth only > allows 75. The latest RFC[1] actually specifies this as 256 *octets* with max of

Re: authentication by email

While, I generally agree with the current approach, especially this close to release. I'm going to play devil's advocate for a bit. Schema migrations have been talked about for quite a while. There are at least 3 external implementations I know of: South, nashvegas, and django-evolution. I'm

Re: authentication by email

On Fri, Mar 9, 2012 at 3:52 PM, Luke Plant wrote: > On 09/03/12 14:49, Tom Evans wrote: > >>> Yes, since no one needs it. Okay no one isn't true, but no one (for true >>> this time) who needed it stepped up and said "I'll implement it and see that >>> it ends up in trunk"

Re: authentication by email

On 09/03/12 14:49, Tom Evans wrote: >> Yes, since no one needs it. Okay no one isn't true, but no one (for true >> this time) who needed it stepped up and said "I'll implement it and see that >> it ends up in trunk" >> > > I'm sorry, that completely mis-characterises the situation. Lots of >

Re: authentication by email

On Fri, Mar 9, 2012 at 3:36 PM, Luke Plant wrote: > What you are really saying is this: being pragmatic means that we > prioritise *your* immediate need above the need to keep the code and the > docs maintainable, and above the need to maintain compatibility with > existing

Re: authentication by email

On 09/03/12 09:37, Clay McClure wrote: > Who's talking about a migration? I'm asking for something that will work > for *new* installations; existing installations can continue > authenticating against usernames for all I care :) > > Moreover, I'm thoroughly frustrated by the fact that

Re: authentication by email

On Fri, Mar 9, 2012 at 8:13 AM, Florian Apolloner wrote: >> Should these things really take five years? What happened to pragmatic? > > > Yes, since no one needs it. Okay no one isn't true, but no one (for true > this time) who needed it stepped up and said "I'll implement

Re: authentication by email

o existing databases have to change? We're talking about leaving User as-is, by default, but providing a mechanism to use a different model if the developer chooses. Clearly this is a decision the developer would not take lightly: you're not going to change from username authentication to email

Re: authentication by email

My django-email-login app ( https://bitbucket.org/tino/django-email-login/overview) does this by putting a hash of the email adress in the username field. It isn't as nice as it could be, but it works. I would really like to see this solved another way, but it is a hard problem with the current

Re: authentication by email

On Fri, Mar 9, 2012 at 21:13, Florian Apolloner wrote: >[...] > Yes, since no one needs it. Okay no one isn't true, but no one (for true > this time) who needed it stepped up and said "I'll implement it and see that > it ends up in trunk" It's the "required" of username

Re: authentication by email

Hi, On Friday, March 9, 2012 6:54:16 AM UTC+1, Clay McClure wrote: > > if settings.AUTH_EMAIL_AUTHENTICATION: > Hell, not another ugly setting like this. Should these things really take five years? What happened to pragmatic? > Yes, since no one needs it. Okay no one isn't true, but no one

Re: authentication by email

On Fri, Mar 9, 2012 at 20:01, Donald Stufft wrote: > The major issue is that there is no way to do schema migrations in core > (currently). So there's no way to handle increasing the length of the > username field. I don't understand what the "username" field length has

Re: authentication by email

rapid >> development and clean, pragmatic design"—unless you want to do something >> seemingly simple like using email addresses for authentication, in which >> case you need to monkey patch models and forms to get everything working >> right, which is neither rapid n

Re: authentication by email

net> wrote: > "Django is a high-level Python Web framework that encourages rapid > development and clean, pragmatic design"—unless you want to do something > seemingly simple like using email addresses for authentication, in which > case you need to monkey patch models and for

Re: authentication by email

, Clay McClure wrote: > "Django is a high-level Python Web framework that encourages rapid > development and clean, pragmatic design"—unless you want to do something > seemingly simple like using email addresses for authentication, in which case > you need to monkey patch m

Re: authentication by email

"Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design"—unless you want to do something seemingly simple like using email addresses for authentication, in which case you need to monkey patch models and forms to get everything work

Re: authentication by email

Key. " Thanks Russell and I wish you good luck in the Django sprints! - Wim On Aug 26, 5:23 pm, Wim Feijen <wimfei...@gmail.com> wrote: > Hello, > > In the past hour, I did some research on authenticating by email and I > believe Django users would benefit a lot if email a

authentication by email

Hello, In the past hour, I did some research on authenticating by email and I believe Django users would benefit a lot if email authentication was included in contrib.auth . Many people have been working on it, and the latest code I could find is here: https://gist.github.com/586056. I am

Re: Authentication using email

Any updates on this one? http://code.djangoproject.com/ticket/8274 Looks like it's still not in the trunk yet? -Aaron On Mon, Aug 18, 2008 at 7:13 PM, Jesús Del Carpio <[EMAIL PROTECTED]> wrote: > > Hello Antonio, > > I am in the exact situation as you mention, I used a snipped in >

Re: Authentication using email

Hello Antonio, I am in the exact situation as you mention, I used a snipped in http://www.djangosnippets.org/snippets/142/ But as you mention, it doesn't work with Admin. What we're doing is log in via the application and since we have the session, jump to the Admin url to be logged. I didn't

Re: Authentication using email

On Aug 19, 8:19 am, Antonio Ognio <[EMAIL PROTECTED]> wrote: > In the login form I ask the user to type an e-mail address and then I > wrap the view at django.contrib.auth.views.login with another view > that copies the POST QueryDict of the request in order to make it > mutable and have the