A given entity could be either a SCIM Client or a SCIM Service Provider for any given transaction. But the same entity could be both a SCIM Client AND a SCIM Service Provider depending on who initiates the transaction.
Most of the information provided is on SCIM 2.0.
The SCIM specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models.
SCIM intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model, as well as binding documents to provide patterns for exchanging this schema using standard protocols. In essence: make it fast, cheap, and easy to move users in to, out of, and around the cloud.
SCIM: Why It’s More Important, and More Simple than you think#Why It’s More Important, and More Simple than you think
Why SCIM 1.1 will not work#From an Organizational Entity perspective, SCIM 1.1 does not support HTTP PATCH but only HTTP PUT. So adding a single SCIM User to a SCIM Group requires replacing the entire SCIM Group. When there might be 10,000 users this is not a reasonable expectation.
More Information#There might be more information for this subject on one of the following:
- Enterprise Cloud Subscriber
- Neo-Security Stack
- OpenID Connect Profile for SCIM Services
- SCIM 2.0
- SCIM Attribute Extensions to Resources
- SCIM Attributes
- SCIM Available Endpoints
- SCIM Client
- SCIM Common Attribute
- SCIM Create Request
- SCIM Discovery Mechanisms
- SCIM Filtering
- SCIM Group
- SCIM Password Management Extension
- SCIM Read Request
- SCIM Replace Request
- SCIM Resource
- SCIM Resource Operations
- SCIM ResourceTypes endpoint
- SCIM Schema
- SCIM Search Request
- SCIM Service Provider Configuration Endpoints
- SCIM ServiceProviderConfig endpoint
- SCIM Use Cases
- System for Cross-domain Identity Management
- Web Blog_blogentry_030117_1