#dominoforever | Product 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

Domino Server command to clear Domino HTTP User Cache

When changing an Internet Password for a user, the new password will not take effect as long as there is an active session in the Domino HTTP User Cache.
This prevents eg Verse Mobile users from getting challenged to change their password immediately after changing their Internet Password, which results in confusion if user is challenged hours after having changed their password.
Currently there is not other way than disabling the HTTP User Cache or restarting the HTTP task; both not valid options for a production environment.
Thus there is an urgent need to have the possibility to flush the HTTP User Cache via a Server Command.
This is possible already for the NameLookup Cache (with "show nlcache reset") and we would expect some kind of "tell http usercache reset" along with "tell http usercache show" etc. for achieving this for the HTTP User Cache.
Also a "tell http usercache reset <userid>" would be very helpful as this should not impact the cache for any other users.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 31 2018
  • Needs review
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    11 Sep 02:03pm

    Maybe the problem is an other thing! After changing a password we use to force the following adressbook views to refresh (in the main adressbook and secondary adressbook if applicable):
    - ($Users)
    - ($ServerAccess)
    - ($LDAPCN)

    This, together with "show nl cache reset", leads to having the new set password nearly instantly working.

    Instead of having the whole names lookup cache reset there should be also an command for a single user like "show nlcache reset <username>"

    However, you are right - this behaviour needs improvment!

    Mark Reiser

    sirius-net GmbH