<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
0D51Y000096NQpVSAWOkta Classic EngineIntegrationsAnswered2023-03-29T05:05:01.000Z2020-07-29T09:54:07.000Z2020-07-31T19:23:50.000Z

dalipk.43271 (Customer) asked a question.

How OKTA put the encrypted package into device clipbaord while android device trust?

I was trying to maintain an android device trust using OKTA.I have seen the flow diagram provided by OKTA. In which you are saying that OKTA put the encrypted package into device's clipbaord.

I am little confuse here.. by which communication method OKTA put this package ?

 

Thanks

Dalip


  • User15851122134349081871 (North Central-Enterprise)

    I assume you mean the diagram at this page? https://help.okta.com/en/prod/Content/Topics/Mobile/dt-mdm-managed-android-devices.htm

     

    That procedure assumes that you've integrated Okta with a 3rd-party Mobile Device Management (MDM) system, like AirWatch/Workspace ONE, MS Intune, or MobileIron). I don't know the details of how those MDM systems communicate to mobile devices they manage, and they may differ, but Okta would do it via that integrated MDM platform and its server-to-device-client protocols. The arrow on that diagram doesn't exactly show this, though.

    Expand Post
  • dalipk.43271 (Customer)

    @User15851122134349081871 (North Central-Enterprise)​  Yes, I am talking about that diagram only. So you means OKTA communicate with device through MDM (Intune, Airwatch) ?

    And Correct me i am wrong So Okta first provide the encrypted payload to MDM and MDM puts that package to device clipboard. is it?

    and my second question is that how OKTA mobile knows that a item has been put into device clipbaord ?

    Expand Post
    • User15851122134349081871 (North Central-Enterprise)

      I'm sorry, I don't know the exact architecture of how the MDM integration works, but I don't think Okta actually sends the package to the MDM system which then sends it to the device, I think that the Okta-MDM integration authorizes Okta to do this directly to the mobile device. I'll try to find out more.

       

      The other steps required in that Device Trust flow ensure that the package was put into the clipboard: if it wasn't, then Okta Mobile would be unable to read it (step 7 in the diagram) and the other steps wouldn't follow and the device would remain untrusted and not permit SSO.

      Expand Post
    • User15851122134349081871 (North Central-Enterprise)

      I found some more info. The device trust flow looks like this, which is exactly like the diagram we already referenced, but it confirms that it doesn't need to go through MDM for this part, Okta Mobile does it all.

      1. A user opens an Android app that has authentication enabled; the user is redirected to Okta for that authentication.
      2. JavaScript on the device's mobile browser will copy token info (that "encrypted payload", above) to the device's clipboard.
      3. Okta Mobile, which listens to the device clipboard, detects the newly pasted info.
      4. Okta Mobile extracts that token info and creates OAuth requests with management hints.
      5. Okta Mobile sends the request to the Okta platform to authenticate the client.
      6. On the Android browser a JavaScript polling process pulls the OAuth result every few seconds. If the result is positive, the user will be redirected to the target app.
      Expand Post
This question is closed.
Loading
How OKTA put the encrypted package into device clipbaord while android device trust?