<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
0D54z00007dFKhACAWOkta Classic EngineAuthenticationAnswered2022-05-18T08:24:21.000Z2022-05-11T02:42:52.000Z2022-05-18T08:24:21.000Z

RaviS.80313 (Customer) asked a question.

Default routing to IWA Agent Authentication instead of Agentless DSSO Authentication

Enabled Agentless DSSO authentication type but by default few users it's redirecting to on-prem IWA Authentication type. We didn't see any discrepancies from their logs.

 


  • Mihai N. (Okta, Inc.)

    Hi @RaviS.80313 (Customer)​ , Thanks for taking the time to reach out to the Okta Community!

     

    Double check the routing rules configuration under your Okta Admin Dashboard→ Security→ Identity Providers→ Routing Rules Tab. Docs can be found here:

     

    https://help.okta.com/en/prod/Content/Topics/Security/configure-routing-rules.htm

     

    First, if you have multiple routing rules make sure that the affected users don't somehow fall under a rules that is higher in priority than the one you expected.

     

    Then you can go step by step and confirm the usual culprits like IP/Network Zones configuration and "USER MATCHES" condition in case you have a custom Regex or attribute configured.

    The other rule conditions should also be validated if the above has be already confirmed.

     

     

    Hope it helps! 

    Expand Post
  • RaviS.80313 (Customer)

    Hi MihaiNegoita,

     

    Thanks for your swift response. As per your suggestion we have validated our routing rule and it's configured as per Okta recommendation.

    As per our analysis

    1. The AWS Workspace users when they connecting from Chrome InCognito browser by default AgentlessDSSOPrecheck steps is failing with StatusCode: 401 error and as per failover configuration it's redirecting to IWA Authentication but this failure was not captured in Okta logs but we have identified from developer tool feature in InCognito window browser.
    2. Same user when they are connecting from normal Chrome browser window instead of InCognito window the AgentlessDSSOPrecheck authentication was working fine and no issues.
    3. This scenario only few AWSWorkspace users are facing this issue and rest of the AWS Workspace user connecting from InCognito browser window it's working fine.

     

    We need your support is there anything(Attribute,Policy) we need to specifically handled in Incognito browser window for AgentlessDSSO Authentication Implementation.

    If you need any additional information then please let me know.

     

    Expand Post
  • RaviS.80313 (Customer)

    Hi Mihai Negotia,

     

    We have verified the AmbientAuthenticationInPrivateModesEnabled and the value was set it 1 in chrome browser. Actually the user when he connected from Chrome browser the agentlessDSSOPrecheck step completed successfully with status code 200 but the same user when he connected from Chrome InCognito window the agentlessDSSOPrecheck got failed and the status code is 401 in browser trace.

     

    Kindly let us know anything else is causing this issue

    Expand Post
This question is closed.
Loading
Default routing to IWA Agent Authentication instead of Agentless DSSO Authentication