HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
This request was targeted for Internet Users Only. The article you point to has the following:
This feature is ignored for authentication of the following users:
Notes® client users
Internet-only users without Notes® IDs
Users who authenticate via SAML federated identity authentication
These are the user's (the one that this capability ignores) that this request is targeted for. We use Domino (Internally) via the browser ONLY. We have external users who do not have a Notes ID who have to authenticate. Therefore the feature you point to does not apply to our users, yet our Security rules (where we have to manually write custom forms to apply our company's password security) do apply. At the moment we have to continually submit a RISK Acceptance on behalf of Domino HTTP inadequacies. These RISK Acceptance only get approved so many times before they say Rejected.
Since Domino V11 you can authenticate internet users with the Notes ID password
https://help.hcltechsw.com/domino/12.0.0/admin/conf_authenticate_webusers_with_notesids.html
We'd like to eliminate the internet password completely in the future, so changing the status to "unlikely".
I need this feature
Also adding common know password list as pre-check when users changes the password, they should be allowed to use thos commonly know password
I would like to suggest that the internet password security also includes setting minimum password length, enforcing Upper and Lower case, enforcing Special Characters, enforcing Numbers in the password.
Also if possible can multi factor authentication be developed at the same time (I have been advised by support that this has also been requested as a development enhancement).
Yes,the function is needed!
And adding complexity policy number of chars, upper lower soecial sign complex checks. Expired password checks with enforeced change.