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
We agree that this would be a great thing to be able to do, however there are a bunch of reasons that make this unachievable for us.
Thomas Hampel's blog post may help some people get past the first part of this idea. https://blog.thomashampel.com/blog/tomcat2000.nsf/dx/shared-logon-failed-with-this-id-after-setting-enableusingappdataforroaming1.htm
Some of the technology used to create the .bin files, in part, resides in Windows. Thus if you are changing/upgrading to a different version of Windows, so of that technology also changes with the change/upgrade. Therefore the .bin file will most probably not work anymore in the new environment and will need to be recreated. As we have no control over what Microsoft do in Windows, we are unable to guarantee that .bin files will persist from version to version.
Sadly, marking this as "No plans to implement".
Yes, most of my customers (all of those who use "SSO") still use Common Login (the one with the windows service), because this works - most of the time, although it is unsupported for current OSs.
They hesitate to go to Notes 12 where this feature is not available anymore...
Same here! I have several customer situations where they facing this issue.
In fact, some customers think to disable NSL and force all users to use a password until all users moved to the new environment before they activate NSL in the new environment again. Sad but true.
greets
Marc Thomas (panagenda)