Firstly, I think this query really belongs in django-users ... this list
is about development _of_ django, not _with_ django.
Secondly, why not override get_form_kwargs [1] to add the user into
creating the form class?
But yes, validation all belongs inside the form class, ideally.
[1]
https://
I guess this is your ticket here:
https://code.djangoproject.com/ticket/23981
I couldn't reproduce the issue so please provide more details.
On Wednesday, December 10, 2014 2:19:41 PM UTC-5, Paulo Maciel wrote:
>
> I put in *db_table* the table name with the new label prefix and it
> works, it
I've researched a little more, and looks like there is BACKEND_SESSION_KEY
so it is possible to annotate user with backend on subsequent requests.
https://github.com/django/django/blob/master/django/contrib/auth/__init__.py#L169
Look like it should be a one line fix for this like
user.backend = ba
All right, that's what I've missed. Thank you, for this point.
Existing LDAP backends I've reviewed do not support password change/reset
at all.
On Thursday, December 11, 2014 7:49:05 PM UTC+4, Tim Graham wrote:
>
> User is only annotated with backend when calling authenticate(). On
> subseque
User is only annotated with backend when calling authenticate(). On
subsequent requests, or in non-request situations like the Python shell,
how will you know which backend to delegate to?
How do existing LDAP backends deal with this problem? (or do they just
ignore it?)
On Thursday, December
Hello,
This is my fist post, so I'm not fully aware of any posting policies you
have, but at least I'll try to present my ideas in clear way.
*Very brief description of what I suggest:*
Optionally delegate password change and password reset to authentication
backend.
*Motivation:*
Django
