Check for password strength at login
Bug #1013786 reported by
Kathy Lussier
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Evergreen version: 2.2 RC1
Currently, tpac does not check a patron's password strength at login as was done in jspac. This wishlist request is for tpac to also check for password strength, and, if it does not meet the password requirements of the system, prompt the patron to change his/her password. This feature is useful because libraries might be registering users with weak passwords with the expectation that the password will be changed as soon as the patron logs into the catalog for the first time.
Changed in evergreen: | |
milestone: | 2.3.0-alpha2 → 2.3.0-beta1 |
importance: | High → Medium |
Changed in evergreen: | |
milestone: | 2.3.0-beta1 → 2.3.0-beta2 |
Changed in evergreen: | |
milestone: | 2.3.0-beta2 → 2.3.0-rc1 |
Changed in evergreen: | |
milestone: | 2.3.0-rc1 → 2.3.0 |
Changed in evergreen: | |
milestone: | 2.3.0 → 2.3.1 |
Changed in evergreen: | |
milestone: | 2.3.1 → 2.4.0-alpha |
tags: | added: jspacremovalblocker |
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
Changed in evergreen: | |
milestone: | 2.4.0-rc → 2.5.0-alpha |
Changed in evergreen: | |
milestone: | 2.5.0-m1 → 2.5.0-m2 |
Changed in evergreen: | |
milestone: | 2.5.0-m2 → 2.5.0-alpha1 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha1 → 2.5.0-alpha2 |
no longer affects: | evergreen/2.2 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha2 → 2.5.0-beta1 |
Changed in evergreen: | |
milestone: | 2.5.0-beta1 → 2.5.0-rc |
Changed in evergreen: | |
milestone: | 2.5.0-rc → 2.next |
Changed in evergreen: | |
milestone: | 2.6.0-alpha1 → none |
Changed in evergreen: | |
milestone: | none → 2.6.0-beta1 |
Changed in evergreen: | |
milestone: | 2.6.0-beta1 → 2.next |
no longer affects: | evergreen/2.3 |
no longer affects: | evergreen/2.4 |
no longer affects: | evergreen/master |
Changed in evergreen: | |
milestone: | 2.next → 2.9-alpha |
Changed in evergreen: | |
milestone: | 2.9-alpha → 2.9-beta |
tags: | added: pullrequest |
Changed in evergreen: | |
milestone: | 2.9-beta → 2.next |
Changed in evergreen: | |
assignee: | nobody → Christine Burns (christine-burns) |
tags: | added: signedoff |
Changed in evergreen: | |
assignee: | nobody → Erica Rohlfs (erohlfs) |
tags: | removed: needstest |
tags: | added: needstest |
tags: |
added: needsrepatch removed: signedoff |
Changed in evergreen: | |
assignee: | nobody → Chris Sharp (chrissharp123) |
Changed in evergreen: | |
assignee: | Chris Sharp (chrissharp123) → nobody |
tags: |
added: needswork removed: needsrepatch |
summary: |
- tpac: Check for password strength at login + Check for password strength at login |
tags: | added: privacy |
Changed in evergreen: | |
status: | Confirmed → Won't Fix |
milestone: | 3.next → none |
To post a comment you must log in.
+1 on this
I hate the idea that people will get their initial 4 digit pin and never be forced to change it when we migrate to a later 2.x release.