<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
0D51Y00008W9xxHSAROkta Classic EngineMulti-Factor AuthenticationAnswered2020-05-20T18:31:35.000Z2020-05-13T11:34:17.000Z2020-05-20T18:31:35.000Z
  • DanSacui (Vendor Management)

    Hello Taylor,

     

    Changes made by Google prevent Android 10 devices from communicating their trust posture (Trusted/Not-Trusted) to ISVs such as Okta. Consequently, authentication requests from Native Apps or Chrome on Android 10 devices appear as "Not Trusted." In this scenario Okta prompts users to access protected resources through Okta Mobile to ensure that device posture is evaluated correctly.

     

    Looking at the Okta Road Map, there is no mention of anything due to be released in regards to Android 10 possibly due to limitations, however I would recommend filing for a feature request so that this is considered in the future. If logged as a FR, there is a good chance this will be addressed.

     

    Many Thanks,

    Dan

    Expand Post
    • Taylor Higley (Customer)

      Thanks, I have since heard rumblings that this gap will be filled in OKTA Identity Engine in late 2020.
  • User15851122134349081871 (North Central-Enterprise)

    I wrote this repose to a similar post of yours Taylor, but will repeat it here:

    Our Product Managers for device management are working to have Okta FastPass handle this for Android 10 (and some previous versions) instead of Device Trust. Caveats: that's still very much in development so we can't yet commit to it yet, or to timelines, but there is a plan to close that gap. Stay tuned!

    Expand Post
This question is closed.
Loading
Android 10 Device Trust Future