Okta Agentless DSSO Authentication Flow Fails to Trigger Automatically
Last Updated:
Overview
Okta fails to route users to the Agentless Desktop Single Sign-On (ADSSO) authentication flow after administrators enable the setting and complete the prerequisite setup in Configure Agentless Desktop Single Sign-On. This occurs when an administrator deletes the default routing rule created during the initial configuration. Resolve this issue by manually creating and activating a new ADSSO routing rule in the Okta Admin Console.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Agentless Desktop Single Sign-On (ADSSO)
- Routing Rules
Cause
An administrator deleted the default routing rule generated during the initial ADSSO configuration. Disabling and re-enabling ADSSO does not recreate the routing rule, as Okta only generates the default rule during the first activation.
Solution
How is the issue of the Agentless DSSO flow failing to trigger automatically resolved
Navigate to the routing rules in the Okta Admin Console, configure a new rule for Agentless DSSO based on the appropriate network zones, and activate the rule as detailed in either the video demonstration or the written instructions.
- In the Okta Admin Console, navigate to Security > Identity Providers > Routing Rules.
- Select Add Routing Rule.
- Configure the routing rule based on the Network Zones as shown in the following image:
- Choose AgentlessDSSO from the Use this identity provider dropdown menu.
- Select Create Rule.
- Select Activate to activate the rule and move it to the highest priority, depending on the use case. If the rule will be activated at a later time, select Don't Activate.
