> Which makes me wonder if the "right" way is to use a custom user > validation system, likely with the e-mail field dropped, or maybe just > aliased to the username so things that expect e-mail address find one.
This is exactly how I solved this problem. I just created an authentication backed that compares the entered username with the email field on the User model instead of the username field but otherwise works just like the standard one. I then arranged to populate the username field with the first 30 characters of the email address to make it easy to find the users in the admin interface and such. The other thing I needed to do was override the default login forms, because they place a maximum length of 30 characters on the username field. Documentation for custom auth backends is at http://docs.djangoproject.com/en/dev/topics/auth/#writing-an-authentication-backend . Hope this helps! /David Christiansen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=.
