<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
0D50Z00008S4ZKMSA3Okta Classic EngineSingle Sign-OnAnswered2024-03-25T19:46:21.000Z2018-10-15T17:58:27.000Z2018-11-02T20:00:07.000Z

pnz85 (pnz85) asked a question.

Okta authentication works well in IE 11.6 but doesn't work with IE 11.0

I am able to use Okta for multi-factor authentication in IE 11.6. After the SMS authentication I am redirected back to my application. But in IE 11.0 I get the IDX10311 error

 


  • Hi,

     

     

     

    My name is Silviu and I am a Technical Support Engineer (Tier II) at Okta.

    According to our documentation we do support the versions of IE you mentioned above. The IE v.9 was the last one to be deprecated.

    In case there is an error thrown when getting MFA from Okta through such a browser, please open up a case with Okta Support and get all the necessary pieces of information in there , as it could be something residing on our end or on the browser itself, but we need a more in-depth look upon it and trace it to the root-cause.

    If I am to pinpoint towards the issue, that could be in regards to a unique arbitrary value that got mixed in the process, most probably a Crypto Nonce failing in the communication process.

    On the other hand, are you sure the browser is compatible to the standard of security we have? Is the page rendering at all? Are you doing an SP-initiated flow and maybe not even getting displayed our content out of our CDN?

    If upon an nslookup cmdlet - your org domain is routed through a (tng) root on the cdn, that means that the communication protocol in exchanging requests with Okta is TLS 1.2. You have to be sure both the client-side and server-side clients are defaulted to a Transport Layer Security of the aforementioned version in regs and also have the SchUseStrongCrypto key of the .NET Framewrok on the version 4.0 set to dword 00000001. Besides this, the Proxy Settings of IE have to accept TLS 1.2, but also TLS 1.0 or 1.1 if the requests are coming from apps not supporting the 1.2 version of the Security protocol yet. The browser will leverage the encryption to the upper layer and default it due to the client-side reg keys changed in the Windows 'regedit' section.

     

    The above may be a far shot or not, but all in all, please open up a case with us and we'll take it from there.

     

    Wish you all the best in your work, Abhishek!

     

     

     

    Thank You,

    Silviu Muraru

    Technical Support Engineer, Okta Inc.

     

     

     

    Expand Post
    Selected as Best
  • Hi,

     

     

     

    My name is Silviu and I am a Technical Support Engineer (Tier II) at Okta.

    According to our documentation we do support the versions of IE you mentioned above. The IE v.9 was the last one to be deprecated.

    In case there is an error thrown when getting MFA from Okta through such a browser, please open up a case with Okta Support and get all the necessary pieces of information in there , as it could be something residing on our end or on the browser itself, but we need a more in-depth look upon it and trace it to the root-cause.

    If I am to pinpoint towards the issue, that could be in regards to a unique arbitrary value that got mixed in the process, most probably a Crypto Nonce failing in the communication process.

    On the other hand, are you sure the browser is compatible to the standard of security we have? Is the page rendering at all? Are you doing an SP-initiated flow and maybe not even getting displayed our content out of our CDN?

    If upon an nslookup cmdlet - your org domain is routed through a (tng) root on the cdn, that means that the communication protocol in exchanging requests with Okta is TLS 1.2. You have to be sure both the client-side and server-side clients are defaulted to a Transport Layer Security of the aforementioned version in regs and also have the SchUseStrongCrypto key of the .NET Framewrok on the version 4.0 set to dword 00000001. Besides this, the Proxy Settings of IE have to accept TLS 1.2, but also TLS 1.0 or 1.1 if the requests are coming from apps not supporting the 1.2 version of the Security protocol yet. The browser will leverage the encryption to the upper layer and default it due to the client-side reg keys changed in the Windows 'regedit' section.

     

    The above may be a far shot or not, but all in all, please open up a case with us and we'll take it from there.

     

    Wish you all the best in your work, Abhishek!

     

     

     

    Thank You,

    Silviu Muraru

    Technical Support Engineer, Okta Inc.

     

     

     

    Expand Post
    Selected as Best
  • mike.davie1.5312945692819849E12 (Customer First Programs)

    Hello Silviu,

     

    Thanks for posting your inquiry in Okta Community Portal.

     

    If you receive a great answer to your question(s), please help readers find it by marking it the best answer. Hover over the answer and click "Best Answer."

     

    Thank you,

    Mike Davie

    Okta Help Center

     

    Expand Post
This question is closed.
Loading
Okta authentication works well in IE 11.6 but doesn't work with IE 11.0