We are building a SCIM connector with Okta as Identity Provider. As per spec, Okta only updates target if there are any changes in the directory.
Say there’s no change once a directory is synced to target/service-provider. Does okta send any heartbeat messages to check the connectivity? We’re trying to differentiate between a steady-state (no changes in directory) vs API failures (like invalid token). Sorry if this is already answered elsewhere.
The Okta SCIM cloud client does not send heartbeat/ping messages to a SCIM server. The only time a connection is initiated is when Okta needs to make an update to a SCIM resource.
Our SCIM implementation only supports inbound SCIM, i.e get data from Okta to our service. Not sure, how “To Okta” works here as there’s no outbound SCIM from our service.
Does “To Okta” mean that when admin assigns a user/group to our app in Okta, those are synced to Okta SCIM processor?