System for Cross-Domain Identity Management (SCIM) is a standard protocol/API for user provisioning. SCIM is now supported by most major identity providers, including but not limited to Azure AD, Okta, OneLogin etc. 

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 https://kantega-sso.atlassian.net/wiki/spaces/KSE/pages/1868075/API+Connectors which rely on full synchronization/snapshotting. In SCIM, only specific changes need to be transmitted 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. While SCIM v1.1 may also work for other providers, we cannot guarantee this and do not officially support it.

SCIM support is currently not available for Bamboo and Fisheye/Crucible, nor is it being actively developed for these apps at the moment. Please get in touch at atlassian.support@kantega.no and add your vote if you would like SCIM support for these applications.