hyerl (hyerl) asked a question.
Okta Identity Engine upgrade - Will Okta Classic APIs work on Okta Identity Engine (OIE)?
The FAQs (https://support.okta.com/help/s/article/FAQs-about-the-Okta-Identity-Engine-upgrade?language=en_US) say:
"All of the legacy APIs will continue to work on Okta Classic."
Does that mean that all of the legacy APIs will continue to work on Okta Identity Engine also?
I check the next question, some feature will deprecated. it seems need confirm with Okta field and upgrade teams.
Will all of the Okta Classic Features be supported in the Okta Identity Engine?
No, not all of the Okta Classic features will be supported in the Okta Identity Engine. Most will be supported, but some of the features are being deprecated in Okta Classic. In most cases, there will be a comparable feature your org can use. The Okta field and upgrade teams will let your org know which features won't be supported and will provide steps to move onto new features.
Thanks for the reply! I understand some of the features will be changing, but you know if the APIs are changing?
If the feature exists in both its leveraging the same API endpoint with the same calls. If the feature exists in classic and not OIE then the call won't work in OIE and vice versa.
A good example of this is "Devices" which doesn't have classic functionality. The API documentation indicates its specifically for OIE only:
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
May Okta Community Buzz
Stay ahead of the curve with Okta for AI Agents, new Okta Learning live sessions and labs, shout-outs, and top trending topics—all aimed at enriching your Okta journey.
If the feature exists in both its leveraging the same API endpoint with the same calls. If the feature exists in classic and not OIE then the call won't work in OIE and vice versa.
A good example of this is "Devices" which doesn't have classic functionality. The API documentation indicates its specifically for OIE only:
https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Device/#tag/Device/operation/listDevices