QQ-I was notified by our Okta team today that we had to make some changes due to the retirement of SF API versions 21-30 which will impact our user provisioning in the future. We ran thru all the release items last release which included this item from a Salesforce perspective. We didn't experience any issues. Apparently if I am understanding correctly, Okta is making some updates upcoming which is forcing the Oauth/connected app vs username/password/token.. This is what was provided to me from the Okta team. https://support.okta.com/help/s/article/FAQs-How-should-Okta-customers-prepare-for-the-upcoming-Salesforce-legacy-API-versions-v21v30-retirement-by-June-2023?language=en_US It seems like a big lift to change all of our environments and it seems like there would be more information out if this was critical of an update for all SF orgs to make if they use Okta. I am looking for guidance from anyone who has dealt/is dealing with this issue as we currently use an Okta Service user account under a API Only profile with tokens for authentication for automatic provisioning of users. Any steps or best practices to make this as easy as possible with minimal impact would be awesome too. Thanks so much in advance and hope someone can help me out :)
Engage with Okta directly for questions related to this upgrade.
The Okta provisioning integration uses the standard Salesforce APIs, just like any other product or integration. Their integration was a using an old version of the Salesforce API. v30 was released in 2014. The current API version is v57.
I am not sure why their integration requires changes in Salesforce. Many other integrated products simply changed their API calls to use a later version of the API and verified their integration still operates properly, requiring no changes.
