#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

Internet Lockout not per server, but per website or per domain.

When you have a clustered Domino backend for hosting websites or web-apps, and you have a loadbalancer in front of them......and internet lockout only occurs per server.....it's possible that you end up on another cluster-member and can continue to login again. The current lockout is based on server, and not on websites|clusters|domains|etc


Please add more options to internet lockout for clustered webaccess like block for entire domain or block for entire website.


  • Guest
  • Jan 14 2022
  • Needs Review
  • Attach files
  • Guest commented
    15 Jan 09:52pm

    @Thomas: what if the database IS replicated, users can logon onto a different server and support tells me to raise an enhancement request because they found several cases for the same problem??

  • Admin
    Thomas Hampel commented
    15 Jan 09:35pm

    Note: The current lockout is based on creating an entry in the inetlockout.nsf. In a distributed environment a different cluster would not know about the lockout until the lock document has replicated.