Okta Connector Updates - Changes in the URL Encoded Query

Hello Everyone,

As per our internal engagement with Okta, we came to know the recent API changes from Okta. There is no public notification or documents around it from Okta side yet. You might have received this update as well if your Okta org is one of the impacted system that might affect after end of . SailPoint is well aware of this change and we are making changes in our connector implementation to handle this end to end before the deadline.

Current Behaviour

The SailPoint Okta Connector is developed as per the best practices and recommended approach from Okta side for using Okta’s Encode Query in the URL. This linked document is still there where it was suggested from Okta to encode the parameters. Certain special characters, such as space, : , ? , or / need to be encoded because they have special meaning in the URL itself.

Upcoming Changes

As per our engagement with Okta, we received a notice from Okta that their API calls will start to fail after 6/28/2024 because of an upcoming change from their side. They will rollout this change as a phased wise manner. As an impact of this change, all the connector functionalities will be affected and operations will be discontinued.

For all requests to /api/v1, Okta is rewriting the URI Path.

For the /api/v1/logs endpoint, where Okta is observing most of the problems, they are implementing a workaround.

Action Items

We are making the necessary changes in the Okta connector and making our connector compatible with this new changes.

For preventing API calls failing, we are updating requests for /api/v1 endpoints.

If there is any customization at your end where you are using these encoded query, please check with Okta and get them corrected.

In order to provide a seamless experience without any downtime, we are planning to release this change in early March in IdentityNow and also with upcoming IdentityIQ patches.

Since Okta has defined a timeline for specific tenants till 28th of June 2024, we will be providing e-fixes for customers who are on IdentityIQ 8.4, IdentityIQ 8.3 and IdentityIQ 8.2 patch levels. You can also check with Okta that whether this change will affect your Org with the mentioned timeline or not. Please request an e-fix by contacting your CSM so that you can get your environment upgraded.

Feel free to reach out us for any query or concern. We will be happy to help you.

Thanks!

1 Like

Hi Dinesh,

Do you have any more details on this, on what is changing in Okta API?

I have looked at Okta documentation and reached out to a few contacts, but there is no mention of this.

Thanks.

2 Likes

Hi Jason,

Found a recent Okta KB mentioning this. Hope this helps.

Best,
Vikram Apte