Skip to Main Content
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

Status Assessment
Workspace Domino
Categories Security
Created by Guest
Created on Aug 28, 2018

Add Password Management capabilities (Expiration) for iNotes/internet users who do not utilize notes clients.

Please expand the current Domino security functionality that expires Notes passwords, to also expire the “Internet Password” without the use of a Notes client. The end result should be that browser-only users will have their “Internet
Password” expire after the grace period set in the person doc, just as Notes client user passwords expire based on the grace period and the “Last change date” in the person doc.

  • Attach files
  • Guest
    Feb 25, 2026

    FYI - security best practices around passwords have changed since the days when passwords were consistently being exposed over plaintext network connections. NIST SP 800-63b actually recommends against forcing periodic password changes.

    https://pages.nist.gov/800-63-FAQ/#q-b05

    "Users tend to choose weaker memorized secrets when they know that they will have to change them in the near future. When those changes do occur, they often select a secret that is similar to their old memorized secret by applying a set of common transformations such as increasing a number in the password. This practice provides a false sense of security if any of the previous secrets has been compromised since attackers can apply these same common transformations. But if there is evidence that the memorized secret has been compromised, such as by a breach of the verifier’s hashed password database or observed fraudulent activity, subscribers should be required to change their memorized secrets. However, this event-based change should occur rarely, so that they are less motivated to choose a weak secret with the knowledge that it will only be used for a limited period of time."