Re: django.contrib.auth and username's field size

On Fri, Aug 2, 2013 at 3:21 PM, Ivan Voras <ivoras@gmail.com> wrote:
> On Thursday, 25 July 2013 23:36:49 UTC+2, jondbaker wrote:
>>
>> Hi Ivan, and welcome. Django >= 1.5 features custom User models, which I
>> believe would solve your problem:
>> https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a-custom-user-model
>
>
> Hello,
>
> I have looked at the documentation basically it looks like too much work for
> a simple thing. Are there any benefits to using the contrib.auth
> infrastructure instead of simply adding an e-mail and password fields to my
> existing model describing a user's profile (except for authorization in the
> contrib.admin app which is nice but will never be seen by my end users)?
>
> In the future I'm planning on adding authentication over Facebook's and
> Google's services (OAuth) - would these kind of things be more convenient to
> do with contrib.auth or my own auth data?
>

If you don't hook in to contrib.auth, then you cannot use libraries
which expect you to use contrib.auth.

Plus, login code is boring and tedious to write, might as well take
advantage of well written alternatives. There is significantly less
work involved in adapting contrib.auth to do precisely what you want
than writing it all from scratch.

Cheers

Tom

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.