Setting up Single Sign-On (SSO)

Single Sign-On (SSO) enables the user to automatically login without having to enter their username or password. The administrator has the option to activate Single Sign-On.

In octoplant 101.3.0, the SSO protocol has changed from strictly Kerberos to the Microsoft Negotiate service. This service then determines whether Kerberos or the NTLM protocol is used.

Note that IP addresses are not supported on Kerberos by default and if used may cause a fallback to the deprecated NTLM.

For more information on MS Negotiate and Kerberos, see:

Microsoft Negotiate - Win32 apps

Configuring Kerberos for an IP address

Requirements

The client and server need to be in the server domain or in a domain with two-way trust.
The client computer is required to be logged into Windows via a user from the Active Directory (AD).
The server service needs to be started using a user from the Active Directory. The user will require an SPN (Service Principle Name) in their attributes.
Active directory users need to have been setup in octoplant.