<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
0D54z00008zy2ZJCAYOkta Classic EngineIntegrationsAnswered2024-04-29T09:03:53.000Z2023-03-30T02:54:23.000Z2023-03-31T19:17:41.000Z

mbv61 (mbv61) asked a question.

Okta to Salesforce API Version Retirement ? and impacts

I reached out to Salesforce and they suggested ask the Okta community. I am trying to understand from a Salesforce perspective what is required with this: 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 SF 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 🙂

 


  • Hello @mbv61 (mbv61)​ Thank you for reacting out to our Community!

     

    At this moment there is no additional guidance, other then the document you have shared.

    However if you do encounter issues, you could open a case with Support.

     

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Expand Post
This question is closed.
Loading
Okta to Salesforce API Version Retirement ? and impacts