feat: generate valid passwords when using additional validators #4
Conversation
(cherry picked from commit d21be1b)
| @@ -11,6 +11,7 @@ | |||
|
|
|||
| from openedx.core.djangoapps.user_api.accounts.utils import handle_retirement_cancellation | |||
| from openedx.core.djangoapps.user_api.models import UserRetirementStatus | |||
| from openedx.core.djangoapps.user_authn.utils import generate_password | |||
@andrey-canon Do you think moving it to eox_nelp and somehow monkeypatch Or do you think using a fork of edx_django_utils and change there |
I think both are valid options, probably the ideal one is to fork edx_django_utils and the make then upstream pr, however I'm not sure if this will be approve, so we could start with the monkey patch approach and then migrate it to edx_django_utils |
|
Reaching the discussion, this PR is closed in favor of eduNEXT/eox-nelp#130 |
Description
(cherry picked from commit d21be1b)
Supporting information
Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.
Testing instructions
install django-password-validators=1.7, set correct settings, add the package to installed apps and migrate it.
Screencast from 22-01-24 15:13:17.webm
Before
Screencast.from.22-01-24.15.10.49.webm
After
Screencast.from.22-01-24.15.15.17.webm
Other information
PRs related
eduNEXT/edunext-platform#676