You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 25, 2022. It is now read-only.
The recently_used validator should only be used when someone is changing their password, not when they are registering. When someone is changing their password they should be logged in, so the request.user object is available. If they are registering, there is no request.user, or it is of the anonymous user. So if the request.user isn't available or is anonymous, then you can skip that validation, and say it passed.
No, I mean that if I use a proper django-passwords validator (for a logged in user) it's no longer possible or easy to access self.user, as is done in the non-proper-django-passwords-validator approach. Either way is probably fine, just would have been nice to cram everything in to a proper django-passwords validator. See: 79d2af3
No description provided.
The text was updated successfully, but these errors were encountered: