Great!
I would like to take a look at any source code you can share.
On Sunday, December 14, 2014 10:10:58 AM UTC+4, Josh Smeaton wrote:
>
> I've been maintaining a custom django backend for quite awhile now. It
> delegates authentication and authorization to an internal API. I do not use
> a c
I've been maintaining a custom django backend for quite awhile now. It
delegates authentication and authorization to an internal API. I do not use
a custom User model at all.
The backend completely handles the reset/change password logic, and the
form uses the methods on the backend directly. I
First, of course I can use custom User model, but two indendetly developed
backends, like backend authenticating against LDAP, and backend
authenticating against custom HTTP service will provide two User models,
each with set_password implementation supporting only one backend and I'll
have to
I've used third party authentication backends, but your request seems a bit
odd to me. I think I'm being caught up on the some of the specifics without
enough context. Why can you not use a custom User that stores the backend
that created it (or last used for authentication) and overrides
set_passw
Yes, I am by no means speaking definitively on the issue -- just voicing
some concerns that I see. I'd love if people with experience with
third-party authentication backends would join the discussion.
On Saturday, December 13, 2014 4:28:52 AM UTC-5, Roman Akopov wrote:
>
> Tim,
>
> It's not abo
Tim,
It's not about the benefit, it's about the possibility. The one simply
cannot use two external backends with support of password change because
each backend will have to provide own User model. I understand your point,
and I agree that some logic I suggest seems controversial, but current
