Making Google Drive API requests using Okta authentication

I’m looking for the best practice to make requests as a third-party app to Google Drive’s APIs that are authenticated with Okta.

Assumptions:

  1. Google’s services are being authenticated using Okta (User go to drive.google.com >> redirect to Okta >> authentication >> Google Drive is available).
  2. We have a public app on Google - all works easily for non-Okta users.

What will be the best practice solution? Creating an Okta app? Exchanging access tokens in runtime? Something else?

Available on StackOverflow as well :point_left:

1 Like

Hi Yalovich, have you made any progress on this. I am working with my developers and in a similar situtation.

Yes. After investigating the main role of Okta in Google Workspace, I found that OAuth 2.0 works as same as it works if Google authenticates the user.

You should trigger a simple authentication with Google, which by the end of the process, you’ll receive an access token you can use.

Actually, Google uses SMAL to authenticate the user and then show a consent screen for additional scopes.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.