Partial SCIM integration for deactivating

Questions SCIM
1

Hi Everyone,

is there a way to partially implement SCIM so it is only used for offboarding? I am looking at this resource, which states that there is a GET request before each PATCH request, which is called to make sure the user exists. Is there a way to configure that GET request in Okta to contain the email address instead of the user id. Like it is used in the Determine if user exists step?

We don’t want to store the users in all of our different environments, because this would be only used internally within our company.

If it is unavoidable what is your recommendation to use Okta as an offboarding tool without implementing fully implementing SCIM/storing users?

Thank your for your time,
Tamas

2

This is not possible. In order for Okta to deprovision a user via SCIM, the user first needs to be provisioned via SCIM. Like you saw, we send update requests using the ID for the user on the SCIM side.

What is your exact use case, and is it something that can be handled using Event Hooks (either handled by Workflows or received by your own server) when a user’s status changes (such as for eventType eq “user.lifecycle.deactivate”)

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.