Skip to main content
Solved

integrating Moveworks and Okta OIG.

  • December 11, 2025
  • 2 replies
  • 58 views
kcrandall
Forum|alt.badge.img

Hey everyone,

 

I have a question for the group that I’m hoping someone may have experience with. We’re planning a governance overhaul this coming year, which will likely include implementing an identity governance (IG) system such as Okta OIG, Lumos, or Zluri IG. Has anyone successfully done this or currently have a setup where Moveworks integrates with an IG platform?

 

Our current plan is to keep Moveworks as the entry point for all software access requests, but then hand off the backend processing and approval workflow to OIG (or whichever IG tool we adopt). Okta and similar platforms offer more advanced capabilities—like time-based access and improved audit controls—which we need for compliance, upcoming security certifications, and more robust user access reporting.

 

If anyone has insights, lessons learned, or is open to sharing how they approached this, we’d love to connect!

Best answer by Kevin Mok

Interesting integration idea ​@kcrandall !

Based on what you are trying to do, I can think of multiple approaches to accomplish this, granted there are APIs available for the platforms you mentioned. I did a quick Google search and saw that Okta OIG has an API, with some endpoints in Beta; Lumos has an API; and Zluri mentions it but does not have public docs.

 

Approach 1:

Use Agent Studio, you can leverage it to connect all the necessary APIs to retrieve software catalogs, make requests to trigger backend processes, etc as long as the APIs allow for that.

 

Approach 2:

Leverage an IT form that contains the list of available software for request (our form finding skill presents the form to the user), and let the ITSM make the correct API calls after the form is submitted. From the looks of it, Okta OIG has an integration with ServiceNow and other platforms, but I am unsure how exactly it works.

 

Overall,  approach 1 makes more sense, since Agent Studio is quite flexible and it allows you to leverage LLMs and create flows to guide your users through the correct path.

    2 replies

    JenHanley
    Forum|alt.badge.img+1
    • JenHanley
    • Community Manager
    • December 16, 2025

    ​@chaney.zimmerman ​@afleury or ​@hundleymf have any of you had experience with this to give some tips to ​@kcrandall ?

    Kevin Mok
    Forum|alt.badge.img+1
    • Kevin Mok
    • Community Manager
    • Answer
    • December 17, 2025

    Interesting integration idea ​@kcrandall !

    Based on what you are trying to do, I can think of multiple approaches to accomplish this, granted there are APIs available for the platforms you mentioned. I did a quick Google search and saw that Okta OIG has an API, with some endpoints in Beta; Lumos has an API; and Zluri mentions it but does not have public docs.

     

    Approach 1:

    Use Agent Studio, you can leverage it to connect all the necessary APIs to retrieve software catalogs, make requests to trigger backend processes, etc as long as the APIs allow for that.

     

    Approach 2:

    Leverage an IT form that contains the list of available software for request (our form finding skill presents the form to the user), and let the ITSM make the correct API calls after the form is submitted. From the looks of it, Okta OIG has an integration with ServiceNow and other platforms, but I am unsure how exactly it works.

     

    Overall,  approach 1 makes more sense, since Agent Studio is quite flexible and it allows you to leverage LLMs and create flows to guide your users through the correct path.

      Terms & ConditionsCookie settingsAccessibility statement