Bug 51403 - Self Service: Expired passwords need to be handled better - "Password Change"
Self Service: Expired passwords need to be handled better - "Password Change"
Status: RESOLVED WORKSFORME
Product: UCS
Classification: Unclassified
Component: Self Service
UCS 4.4
Other Windows NT
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-06-02 17:00 CEST by Michael Grandjean
Modified: 2020-11-10 14:18 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2020-06-02 17:00:00 CEST
UCS: 4.4-4 errata617

Scenario: I use a simple password policy, e.g. minimum length is 8 characters. I have a user whose password expired. This is quite common for new users, when the option "change password at next login" is checked. This user tries to use the Self Service to change their password.

Expected behaviour: The Self Service dialog for "password change" tells me that my password expired. It then offers to change my password and tells me the requirements (e.g. at least 8 characters).

Observed behaviour: The Self Service dialog for "password change" does not tell me that my password expired. Instead it says:
"Invalid credentials. Password change failed."
Comment 2 Michael Grandjean univentionstaff 2020-06-03 00:00:52 CEST
Okay, obviously I ran into Bug #51047. After maneuvering around the Errorcode 20, the error messages regarding the Self Service unfortunately do not improve.
Comment 4 Ingo Steuwer univentionstaff 2020-11-10 14:18:33 CET
We implemented SSO with SAML for the Self Service with Bug #51607. I think the behaviour described here is not the case anymore.

-> WORKSFORME