<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
0D54z00007FeKzTCAVOkta Classic EngineMulti-Factor AuthenticationAnswered2024-09-15T09:01:28.000Z2021-10-22T02:38:54.000Z2022-04-22T18:44:43.000Z
  • Hello, @561oz (561oz)​ 

     

    Thanks for reaching out! I would like to know if you can provide some more details on this so we can help you.

    Any config that you might think is not right or any screenshot will help.

     

    Vicente

    Okta, Inc

    Expand Post
  • 561oz (561oz)

    Here's our current client agent config.

     

    Config: "C:\Program Files\Okta\Okta Windows Credential Provider\config\rdp_app_config.json"

    {

    "Url": "https://XXXXXXXX.okta.com",

    "ClientId": "0XXXXXXXXXXXXXXXXXX97",

    "ClientSecret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX+Q==",

    "FilterCredentialProvider": true,

    "InternetFailOpenOption": true,

    "RdpOnly": false,

    "WidgetTimeOutInSeconds": 180,

    "ErrorTimeOutInSeconds": 30,

    "EnforceTimeoutVersionAgnostic": false,

    "SslPinningEnabled": true,

    "DisplayPasswordResetLink": false

    }

     

    To replicate the issue:

    • From home machine, connect to VPN
    • RDP to work desktop
    • (do some work, send emails, etc.)
    • Lock work desktop RDP session
    • Enter password
      • When Okta widget pops up, click the "X" to close the widget.
      • (This is where the issue is at. The session is logged off, when we want it to just stay locked\disconnect).
    • RDP to work desktop
      • This time, enter password & do auth via Okta
    • The prior user session is gone, and any opened work was lost.

     

     

     

    Expand Post
  • 561oz (561oz)

    I made a case:

    Case  01240186

  • Schrodyr (Freeman)

    Was there a solution for this issue? I'm trying out WCP and getting the same logoff results. Really annoying.

  • User15932079466932298204 (Vendor Management)

    Hello Okta Community!

     

    We have reviewed this internally and after the repro efforts by one of our engineers this behavior comes by design as a security measure. An Okta idea has been created already by the customer Darren DeHaven here: https://ideas.okta.com/app/#/case/142433. If you are seeing this behavior please access the link and up vote the idea so our engineering team can review it and evaluate it for future roadmaps.

    Expand Post
  • pwbo8 (pwbo8)

    I don't think that Okta realizes how this is a bad design, a bad signal to customers and the community overall. The initial problem was reported 6 months ago. No response, no help. Nothing !!!

     

    Very annoying !!!

This question is closed.
Loading
When Okta Windows Credential Provider fails current user session gets logged off