<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
0D54z0000A86FG8CQMOkta Classic EngineIntegrationsAnswered2024-05-08T16:43:40.000Z2024-05-07T18:23:50.000Z2024-05-08T16:43:40.000Z

User1666097899083229944 (Click Armor) asked a question.

SCIM implementation via OIDC

We are a SaaS-platform developer and have some OKTA SSO functionality working for a growing number of clients and we want to build on that, but the OKTA documentation seems to provide conflicting guidance.

 

We offer an educational SaaS platform (focused on cybersecurity awareness training) with some third party integrations for Single Sign on and Account provisioning, using OIDC. We now have OKTA SSO working well, including Just-in-time provisioning. 

 

However, one of our customers has asked how he can deactivate accounts on our platform from his OKTA panel. Since we had already implemented SCIM on Active Directory and can easily deactivate accounts, we thought it would be a reasonably straightforward implementation to get similar SCIM functionality running for our OKTA integration. 

 

We were surprised to learn this week the following

“Adding SCIM provisioning to an OpenID Connect (OIDC) integration is not currently supported.” 

from Add SCIM provisioning to app integrations (https://help.okta.com/en-us/content/topics/apps/apps_app_integration_wizard_scim.htm)

 

This is unexpected. We have used OKTA documentation through many steps of the process. At no point were we made aware that SCIM on OIDC would be a problem. 

 

Can someone explain please which is right? Does OKTA support SCIM for OIDC or not? If not, why don't the other documentation pieces state this limitation more clearly?

If not supported, what other options are available to us? Are we expected now to rewrite our OIDC integration in SAML to support the SCIM use case our client has? 


MatthewH.10249 likes this.
This question is closed.
Loading
SCIM implementation via OIDC