Use Windows desktop single sign-on (SSO) to allow immediate and secure access to resources via Kerberos-based authentication.
To enable this feature on any SecureAuth IdP realm, the SecureAuth IdP appliance must be joined to the company domain. Window desktops must be on the same company domain, with the ability to process and use Kerberos tickets.
You can configure realms to use Windows desktop SSO in any of the following ways:
|Windows SSO||When the Begin Site is configured to use Windows SSO login workflow, you have the option to include multi-factor authentication (MFA) and adaptive authentication. This method is more secure because it includes the Device Recognition layer. |
|Windows SSO (skip workflow)||When the Begin Site is configured to use Windows SSO (skip workflow), it bypasses the login workflow, skips MFA, and routes the user directly to the Post Authentication page once it validates the Kerberos ticket. This method bypasses the Device Recognition layer, however, it increases system performance. |
SecureAuth IdP configuration
- Go to the Workflow tab.
In the Workflow section, set the following:
Set to Username only.
To configure two-factor authentication (2FA), select Username | Second Factor.
|Public/Private Mode||Set to Public Mode Only. |
In the Custom Identity Consumer section, set the following:
|Receive Token||Set to Token. |
|Require Begin Site||Set to True. |
- To include MFA and adaptive authentication in login workflow, set to Windows SSO. This method adds the Device Recognition layer, and is more secure.
- To skip the login workflow and go directly to the Post Authentication page, set to Windows SSO (skip workflow). This method does not include MFA, adaptive authentication, and increases performance.
|Begin Site URL||Depending on the Begin Site selection, this field is auto-populated with WindowsSSO.aspx or WindowsSSO2.aspx.|
|User Impersonation||Set to True. |
|Windows Authentication||Set to True. |
- Click Save.