...
SCIM is a REST-like protocol and works over HTTP(S). The identity provider sends provisioning instructions to registered applications whenever changes occur by calling REST endpoints in the provisioned application (e.g. Jira or Confluence). This can be far more efficient than client-initiated API Connectors which rely on full synchronization/snapshotting. In SCIM, as only actual specific changes need to be transmitted . SCIM is therefore especially recommended for large once initial sync has been established, giving it far betteer scalability characteristics, and is recommended for larger user directories.
Kantega SSO primarily supports SCIM version 2. The older SCIM v1.1 protocol (legacy) is supported and tested for use with Okta's on-prem provisioning agent, and . While SCIM v1.1 may also work for other v1.1 providers, we cannot guarantee it this and do not officially support it.
| Info |
|---|
SCIM support is currently not available in the for Bamboo and Fisheye/Crucible versions of KSSO, nor is it being actively pursued developed for these apps at the moment. Please get in touch at atlassian.support@kantega.no and add your vote if you would like to see this functionalitySCIM support for these applications. |