<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
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D51Y00005tHeAkSAKOkta Classic EngineLifecycle ManagementAnswered2024-04-16T12:03:00.000Z2019-01-16T15:09:23.000Z2021-04-25T22:53:18.000Z

kdlef (kdlef) asked a question.

January 16, 2019 at 3:09 PM
Export and Import Okta Tenant Configs

Hello,

 

Is it possible to export and import Okta tenant configs? Can the state of an Okta tenant be saved, exported, and imported into another tenant? It would be nice to save the state of our Okta Test tenant (as json or something) and store it in GitHub. By doing so, we could re-import the saved state stored in GitHub if our test configs ever strayed too far from our "master" configs. This feature would also be useful when propagating changes up to our Production Okta instance.

 

Best,

Jordan

  • 5 answers
  • 5.25K views

  • sergiu.patrichi1.5245776395516377E12 (Vendor Management)

    Hi Jordan, Sergiu from Okta Support here. At this point, Okta does not provide an out of the box solution for this use case, but there are different workarounds.

    1) If you want to replicate users/groups into a different tenant, you can set up through the use of an Okta Org2Org application, which acts as a Hub - Spoke configuration. It is based on a provisioning API + SAML - Identity Provider configuration. All you need to do is navigate to Application -> Add a New App and search for Org2Org, select the Okta app and follow the setup instructions.

    2) If you want to export the app configuration, that can be done at this point by using APIs

    (GET: https://${org}.okta.com/api/v1/apps/0oa1gjh63g214q0Hq0g4)

     

    All the best!

     

    Expand Post
    Selected as Best

  • sergiu.patrichi1.5245776395516377E12 (Vendor Management)

    Hi Jordan, Sergiu from Okta Support here. At this point, Okta does not provide an out of the box solution for this use case, but there are different workarounds.

    1) If you want to replicate users/groups into a different tenant, you can set up through the use of an Okta Org2Org application, which acts as a Hub - Spoke configuration. It is based on a provisioning API + SAML - Identity Provider configuration. All you need to do is navigate to Application -> Add a New App and search for Org2Org, select the Okta app and follow the setup instructions.

    2) If you want to export the app configuration, that can be done at this point by using APIs

    (GET: https://${org}.okta.com/api/v1/apps/0oa1gjh63g214q0Hq0g4)

     

    All the best!

     

    Expand Post
    Selected as Best

    • fkdv9 (fkdv9)

      Hey Sergui, would the Org2Org, Hub - Spoke configuration be the best approach to migrate from the sandbox to the production environment?

  • kdlef (kdlef)

    Thank you, @Sergiu.

    Just to confirm, there is no standard process for exporting the Application or Security configs (General, AuthN, Delegated AuthN)? For what I'm interested in, I'd have to write a script that hits the tenant's API to grab this information and mold it into something meaningful?

     

    Best,

    Jordan

    Expand Post

  • sergiu.patrichi1.5245776395516377E12 (Vendor Management)

    No problem Jordan. And yes, that information can be obtained through API at this point. There does not seem to be anything related to this on the roadmap, so I would suggest submitting a feature request, if you would like to see this functionality implemented in the future.

     

    Sincerely,

    Sergiu Patrichi

    Expand Post
This question is closed.
Loading
Export and Import Okta Tenant Configs