<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
0D5KZ00000cGddW0ASOkta Classic EngineIntegrationsAnswered2025-04-09T22:45:11.000Z2025-04-09T14:33:41.000Z2025-04-09T22:45:11.000Z

Tam√°sB.04602 (Customer) asked a question.

Partial SCIM API integration - only implement certain endpoints

Hi,

 

I would like to use SCIM integration only internally in my organization for only deactivation of users in my application. My question is that is it possible to only implement the part, which is responsible for the deactivation and leave the rest of the endpoints blank or do I have to implement all the necessary endpoints and not just define them?

 

For example we have users in Okta and they are added manually to my application, which then we want to deactivate when they leave our company.

When we submit this integration is it required that all of the endpoints work? If they are, is there any solution, which can be used as only deactivation of our internal users in our application?


  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hello @Tam√°sB.04602 (Customer)​ , thank you for contacting Okta Community.

     

    When you deactivate a user, Okta sends a PATCH/PUT based on the app they are using, but initial linking between the accounts will be done through GET, which has to be implemented. So, at a minimum, you should be implementing GET (List and Individual) and then PATCH or PUT based on the app type you use.

     

    I advise reaching out via devforum.okta.com  as they will have more insight into this topic.

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Expand Post
This question is closed.
Loading
Partial SCIM API integration - only implement certain endpoints