Authentication system : should I use contrib.auth or reinvent the wheel?

Hi all,

I need an authentication system for my website; quite a common need
today, isn't it?
I have decided to figure out if I can use django.contrib.auth. I
have the following problems :

1. start a new project, and just do the minimum:
*in settings:
- a database
- a template path
- the django.contrib.admin app
*then syncdb
*in urls: uncomment the admin urls
*add in your template folder, the file requested by the view
password_change in contrib.auth.views :
- registration/password_change_form.html
- this file contains a simple text

Problem : trying to access http://<your.site>/admin/password_change
will render -- after login -- your template in registration/
password_change_form.html instead of the admin one. I can't find out
why.

2. strange things in code :
- in contrib.auth there is a UserCreationForm provided, but there
seems to be no view for it or for any signup page.
- in contrib.auth.views, the login sends no error for authentication
failures, and sends the page again silently.

I hope I am wrong in all this, due to the fact that I am a new django
user. Your help is welcome.
Also : instead of contrib.auth, what is generally used for
authenticating users?

Thanks
-- Peyman

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.