<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language

IWA DSSO Agent Reporting Offline in Okta While DSSO Authentication Still Functions

Administration
Okta Classic Engine
Directories
Okta Identity Engine

Overview

The Okta Admin Console reports an Integrated Windows Authentication (IWA) instance as offline, but Desktop Single Sign-On (DSSO) authentication continues to function. This occurs when the Okta AD Agent and Okta IWA Agent are installed on the same host. The following warning appears in the AD Agent logs (default location: C:\Program Files (x86)\Okta\Okta AD Agent\logs):

 

2018-08-31 11:36:06.561 Warning -- {HostName}(5) -- IWA Agent is down. IWA URL: https://<IWAServerURL>. Error: The remote server returned an error: (401) Unauthorized.

 

Resolve this issue by adding the server alias to the approved host list on the server or by disabling the loopback security check mechanism.

Applies To

  • Okta Classic Engine
  • Active Directory
  • IWA Desktop Single Sign-On (DSSO)

Cause

Windows Server's Loopback Security Check mechanism prevents access to a web application using the Fully Qualified Domain Name (FQDN) when the attempt originates from the same server hosting the application and the server's hostname does not match the FQDN. For example, if both the AD Agent and IWA are installed on a server with the hostname ADAGENT and IWA is configured to use the URL https://<iwa_server>.example.com, the Loopback Security Check mechanism triggers when the AD Agent attempts the IWA health check, causing the health check to fail and the server to report as offline.

Solution

How is the IWA DSSO Agent offline status resolved?

Address the Loopback Security Check behavior preventing a successful IWA health check by applying one of the two workarounds that Microsoft recommends.

  • Add the Canonical Name (CNAME) or DNS alias that the host server uses to the approved host list.
  • Disable the loopback check.

Consult the Microsoft Knowledge Base (KB) article for the exact steps to apply the selected workaround.

Loading
IWA DSSO Agent Reporting Offline in Okta While DSSO Authentication Still Functions | Okta Support