iplweb/django-password-policies-iplweb

Django unicode-aware password policies.

django-password-policies

django-password-policies-iplweb is an application for the Django framework that provides unicode-aware password policies on password changes and resets and a mechanism to force password changes.

As for now (Jan 2021), this fork is actively maintained by |iplweb|

Requirements

This application requires Django 2.2 or newer

Documentation

A detailled documentation is available on the project's GitHub Pages.

django-password-policies-iplweb's Issues

How can I use it?

I have install it use pip and then put it in the “installed apps” in settings.py.
I can see it in Admin , but how can it be effect?

Documentation

Is there no documentation for this package?

Tests don't pass with Django 3.1

Tests don't pass with Django 3.1

Shallow Documentation

I have come across this package a fork from the original package hopping to see the changes that have been implemented from the original project. However, there is harly any documentation. The original project is no longer compatible with the latest django packages.

Can you assist on how to install and configure this package on a django project. I am currently on django 5.0.1

Examine and eventually drop django-easysettings dependency

Examine and eventually drop django-easysettings dependency

Django 3.2

Hello, does this package work with Django 3.2?

Bypass AUTH_PASSWORD_VALIDATORS

The setting AUTH_PASSWORD_VALIDATORS was not used when change password.

The form password_policies.forms.PasswordPoliciesForm not use the function django.contrib.auth.password_validation.validate_password to validate the new password.

That could cause an insecure state, becase the final user could think the restriction used in a basic Django are aplied when that not the case.

Also allows to add password validators from 3 parties.

TypeError: Object of type datetime is not JSON serializable

I get this error when I use:
SESSION_ENGINE = 'django.contrib.sessions.backends.db'

This package not support it?

is_authenticated() should be replaced with is_authenticated in django >= 1.10

https://docs.djangoproject.com/en/1.11/ref/contrib/auth/#django.contrib.auth.models.User.is_authenticated

https://github.com/iplweb/django-password-policies-iplweb/blob/master/password_policies/views.py#L35

Missing migrations

I have installed django-password-policies-iplweb 0.8.2 version using pip

Collecting django-password-policies-iplweb==0.8.2
  Downloading django_password_policies_iplweb-0.8.2-py3-none-any.whl (177 kB)

and it seems that some migrations have to be done:

Migrations for 'password_policies':
  /usr/local/lib/python3.7/site-packages/password_policies/migrations/0003_auto_20210713_1349.py
    - Alter field created on passwordprofile
    - Alter field last_changed on passwordprofile

This seems it affects to 0.8.3 version, develop and master branches too.

Environment:

• Debian 10 (buster)
• Python 3.7
• Django 2.2

Use deprecated functions

In Django 3.0 deprecates functions ugettext_lazy and ungettext

User “Zero-cost” exceptions

In python 3.11 are implemented a performance for try blocks:

• “Zero-cost” exceptions are implemented, eliminating the cost of try statements when no exception is raised. (Contributed by Mark Shannon in bpo-40222.)

On the PR #28 the way that manage the Django 3.0 deprecation imports are not use this performance.
We need to reorder the importation in the try block to use that improve.