This article discusses the possibility of setting up a brand new Org2Org Hub/Spoke integration between an Okta Classic org and an Okta Identity Engine (OIE) org and how the features for this integration might change in the context of an OIE upgrade of either the Hub or the Spoke tenant.
- Org2Org app integration
- Okta Integration Network
- Single Sign-On
- Okta Identity Engine (OIE) upgrade with pre-existing Org2Org app integration
- Possibility to setup Org2Org Hub/Spoke integration between an Classic tenant and an OIE tenant
Generally, it is possible to set up Org2Org app integration between a Classic tenant and an OIE tenant in the Hub/Spoke model. Any of the following Hub/Spoke combinations is possible, with not so many differences for the Org2Org app integration:
- Two Classic tenants
- Two OIE tenants
- One Classic and one OIE tenants
However, please be aware of the login policy differences and the GUI difference between an OIE tenant and a Classic tenant.
In terms of Org2Org supported features, there are not many differences between an Org2Org integration with two Classic/OIE Org2Org Hub/Spoke tenants setup and one Classic and one OIE Org2Org Hub/Spoke tenant setup.
Before performing the OIE upgrade for either Spoke/Hub org instance, Okta Administrators should familiarize themselves with the new feature changes for the OIE tenant and how it is different from the Classic one.
For a full list of the OIE tenant feature changes, please read below OIE upgrade documentation:
If there is any specific use case or additional questions about the post-OIE upgrade feature changes, please open a Customer Support Ticket for further assistance.
Related References
- For a full list of Okta Org2Org-supported features, please see Okta Org2Org-supported features.
