Bug 1425412 - [Docs][RFE][Admin] Document that user can reset expired password
Summary: [Docs][RFE][Admin] Document that user can reset expired password
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ovirt-4.1.6
: ---
Assignee: Byron Gravenorst
QA Contact: Avital Pinnick
URL:
Whiteboard:
Depends On: 1037844
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-21 11:54 UTC by Lucy Bopf
Modified: 2019-05-07 12:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-08 12:02:26 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lucy Bopf 2017-02-21 11:54:40 UTC
Previously, if a user password expired, it needed to be reset on the LDAP server. Now there is a new capability added to the LDAP and JDBC extensions to enable changing passwords from the front end in a new change password screen.

The login procedure must be amended to account for a use case where the password is expired and the machine now prompts the user with a password dialogue. Assignee should assess whether this needs to be called out explicitly in the documentation or is clear enough in the UI.

Comment 2 Lucy Bopf 2017-08-11 07:00:29 UTC
Assigning to Byron for review.

Comment 5 Avital Pinnick 2017-09-13 04:59:19 UTC
Yaniv,

Why are we using expiring passwords? The policy of forced password expiry is generally rejected by security experts. I can't think of any good reason for enabling this policy.

https://www.ncsc.gov.uk/articles/problems-forcing-regular-password-expiry

https://cryptosmith.com/password-sanity/exp-harmful/

https://arstechnica.com/information-technology/2016/08/frequent-password-changes-are-the-enemy-of-security-ftc-technologist-says/

Comment 6 Yaniv Lavi 2017-09-13 09:05:08 UTC
Moran, can you comment?


Note You need to log in before you can comment on or make changes to this bug.