Lotus Notes Shared Login - IBM Lotus Notes

Previous versions of the Lotus Notes environment had a single-login feature that leveraged the Lotus Notes ID functionality. An additional set of files and functionality were installed to pass the Windows password to the Client Single Logon feature. When the user logged into a Windows-based workstation, the feature captured the password that was utilized and then presented that password on login to the Notes environment. The standard way to access the Notes environment is to leverage the native password to unlock the ID file.

Lotus Notes Shared Login

The client single-login feature required that the Windows and Notes passwords be synchronized. When either password was changed, the user was required to go through steps to ensure that the password was appropriately passed to the other system to ensure synchronization. As a result, when the password was forgotten and reset from a Windows perspective, the client was unable to access the Domino environment directly without going through a different process to modify the password.

The new Notes Shared Login (NSL) effectively removes the password requirements from the Notes ID and shifts the responsibility for authentication to the Windows login. As a result of the architecture, the Windows platform is the only supported environment; NSL will not work with the MAC or Linux desktop systems. Password changes and resets are conducted through the Windows authentication environment and the credentials are stored on the local machine. As a result, environments such as Citrix and the Notes USB (on a stick) environment are not supported.

Lotus Notes Shared Login

The implementation of the NSL feature is carried out by removing previous implementations of Client Single Logon and the implementation of a policy for users who will be leveraging the NSL feature. The feature is enabled and managed through a security policy. If the environment already has a security policy enabled, it can be modified to enable the NSL feature. As an administrative team, you may choose to implement the NSL feature outside of the current security policies. If this is the case, create a new security policy. The policy allows the administrative team to enable the NSL feature, allowing the users to participate, and allows for the use of standard or custom dialog boxes to activate and deactivate usage.

The policy document shown in the following screenshot outlines the settings that will enable the feature:

The policy document

Once the security policy is enforced, the user will participate in the NSL process. The end user will be notified by a standardized dialog box that they are now participating in NSL (see the following screenshot):

standardized dialog box

If the administrative team allows the end user to make changes to whether they participate in the NSL process, they can modify this setting by accessing the User Security... dialog box, as shown in the following screenshot:

accessing the User Security... dialog box

In the User Security dialog box (as shown in the following screenshot), the option for participating in NSL is identified as Log in to Notes using your operating system login box. The end user can check or uncheck the box as per their requirements:

end user can check or uncheck the box

The new NSL feature can offer an enhanced user experience but requires some planning and implementation across the environment to ensure proper utilization. It will be important to leverage the appropriate resources (online or through a service organization) to ensure the proper implementation of the feature.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Lotus Notes Topics