<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
0D54z00008giK3JCAUOkta Identity EngineWorkflowsAnswered2023-01-20T00:51:21.000Z2023-01-18T22:20:10.000Z2023-01-20T00:51:21.000Z

JacksonK.52224 (Customer) asked a question.

Is there a way for Okta to see newly registered devices in Google Admin?

What I want to do is create a workflow that essentially will pick up newly registered iOS devices, see if the OS is up to date depending on what we put, and wipe it if it isn't.

 

The hard part is trying to figure out how to get Okta to read the user device when it's registered. There is no "when this happens" option in Okta for google admin

 

And I thought I could work around would be look in Google Admin and see if there was anything that can trigger when a new device is created, such as add user to a group or add information to a google sheet. The only thing I see is setting up alerts but that has no information when it's sending out an email, I wish it at least sent out the user's email address that registered the device.

 

Does anyone have a recommendations to look into?


  • TimL.58332 (Workflows)

    @JacksonK.52224 (Customer)​ - Hi,

     

    The type of functionality you were describing "When this happens" is typically because the vendor supports event/webhooks. Part of using those types of cards is functionality that contacts the vendor, sets up the event/webhook with the Workflows card acting as an API endpoint.

     

    For this use case you would need to determine which of the hundreds (possibly thousands) of Google API Endpoints will expose the information you are looking for. Google Oauth Playground:

     

    https://developers.google.com/oauthplayground/

     

    Is a good place to start as it will allow you to easily setup auth, adjust scopes, and make API calls to their service. Assuming there is an API Endpoint that will expose this information, once found, you can then implement the call using workflows to receive and act on the payload.

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    @JacksonK.52224 (Customer)​ - Hi,

     

    The type of functionality you were describing "When this happens" is typically because the vendor supports event/webhooks. Part of using those types of cards is functionality that contacts the vendor, sets up the event/webhook with the Workflows card acting as an API endpoint.

     

    For this use case you would need to determine which of the hundreds (possibly thousands) of Google API Endpoints will expose the information you are looking for. Google Oauth Playground:

     

    https://developers.google.com/oauthplayground/

     

    Is a good place to start as it will allow you to easily setup auth, adjust scopes, and make API calls to their service. Assuming there is an API Endpoint that will expose this information, once found, you can then implement the call using workflows to receive and act on the payload.

    Expand Post
    Selected as Best
  • JacksonK.52224 (Customer)

    Alright thanks, I will look into this. The main reason I'm trying to keep off google api is apparently because the google cloud license and api service account creations costs money and that's something we're trying to avoid.

    • TimL.58332 (Workflows)

      That is definitely going to limit you. The vast majority of API endpoints for google are through GCP. Even some of the Workspace functionality requires domain wide delegation through GCP.

This question is closed.
Loading
Is there a way for Okta to see newly registered devices in Google Admin?