Problem/Motivation

The Password Compatibility module was added in Drupal 10.1.0. When sites are upgraded from older versions of Drupal, the module should be installed automatically, and it allows users to log in with their existing passwords. Once a password has been used with the Password Compatibility module, that password can be used in the future whether or not the module is installed.

Site administrators need some guidance to decide when to uninstall the module.

Proposed resolution

Provide information about how many passwords have not been used since the site was upgraded to Drupal 10.1.0 or later.

There is already a contrib module, Password Stats, that provides this information. We can borrow some of its code and add it to the core Password Compatibility module.

Show additional information

  • On the site status report
  • On the main help page for the Password Compatibility module

Remaining tasks

User interface changes

API changes

None

Data model changes

None

Release notes snippet

N/A

Issue fork drupal-3360854

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

benjifisher created an issue. See original summary.

Arshu1864 made their first commit to this issue’s fork.

catch’s picture

catch
he/him
Primary language English
commented

This is somewhat of a duplicate of #3352094: Notify users that they need to reset their password when it matches an unsupported hash type but there's one part of the issue summary that's not covered here, so I slightly repurposed that issue.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.