The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Hi,
there is a module Password Expire http://drupal.org/project/password_expire that seems to overlap some features of this module.
Shouldn't that module be integrated here?
If not; I think it should be wise to mention the existence of that module here and argue the differences.
Same issue for some other password modules that seem or might overlap; integrate them all? If not; document the differences on this project page?
It's for every user every time again an enormous lot of work to find out which password modules should be used, if there is not an explanation about the differences. And easiest for many new users would be just one module that has it all...
Same for password_change http://drupal.org/project/password_change for more security; Drupal would be more user friendly if this all is in one module
Comments
Comment #1
ClearXS commentedAhh, here is another one that overlaps: http://drupal.org/project/password_strength
And see this old comment of the Password_Expire developer about integration:
merge into password policy - http://drupal.org/node/347243
Comment #2
greg.harveyArguably *all* of this should be in LoginToboggan, one user login settings module to rule them all.
Comment #3
lpalgarvio commentedasked to deprecate password strength:
#833206: deprecate in favor of Password_Policy
merge blocker on password expiry:
#347243: merge into password policy
Password change confirm is a bit abandoned. Dave Reid never added some patches i posted, might be too busy.
better to just work out this on your own and don't count on integration/help. snatch the code ;)
#1234162: integrate Password Policy with Token
#1234164: integrate Password Policy with Rules
#1234166: integrate Password Policy with Actions/Trigger
Comment #4
erikwebb commentedpassword_expire definitely is a massive overlap, but that module looks completed abandoned at this point. I disagree that password_change is obvious overlap.
I'm not sure there is a direct overlap with any of these modules. While the other listed are largely UI-specific additions, Password Policy is designed to ensure certain password characteristics in the database. There's either not enough overlap to worry about or, I agree with greg.harvey, that most of these should be consolidated into a single master module (probably joining the Password namespace for D7).
Comment #5
lpalgarvio commentedwell i've been trying to get the ball rolling out
Password namespace is taken with a module that backports D7 password hashing method to D6.
would it be possible to start some work on merging/creating a new solution using the current namespace for D6 and/or D7?
Comment #6
erikwebb commentedIt seems the best option is to absorb Password Expire as a submodule for a new as-of-yet uncreated 7.x-2.x branch. They currently have no D7 version and there's no reason their code couldn't be integrated here.
Comment #7
erikwebb commentedComment #8
erikwebb commentedComment #9
erikwebb commentedComment #10
greg.harveyCorrect me if I'm wrong, but this seems to be done? There are expiry options already... unless there's something explicitly missing that Password Expire does over the current functionality, move to closed?
Comment #11
erikwebb commentedI just took a second look at Password Expire and I think you're right, there are no substantial differences.
Comment #12
erikwebb commentedI just took a second look at Password Expire and I think you're right, there are no substantial differences.