Difference between revisions of "SCIM 2.0"
(→Context) |
(→Context) |
||
| Line 8: | Line 8: | ||
Developers can think of SCIM merely as a REST API with endpoints exposing CRUD functionality (create, read, update and delete). | Developers can think of SCIM merely as a REST API with endpoints exposing CRUD functionality (create, read, update and delete). | ||
| − | + | The standard is governed by the following IETF documents: RFC 7642, RFC 7643, and RFC 7644. | |
Clearly, this API must not be anonymously accessed. However, the basic SCIM standard does not define a specific mechanism to prevent unauthorized requests to endpoints. There are just a few guidelines in section 2 of RFC 7644 concerned with authentication and authorization. | Clearly, this API must not be anonymously accessed. However, the basic SCIM standard does not define a specific mechanism to prevent unauthorized requests to endpoints. There are just a few guidelines in section 2 of RFC 7644 concerned with authentication and authorization. | ||
Revision as of 20:35, 15 September 2018
Full Title or Meme
System for Cross-domain Identity Management is a means to enable flows of User Private Information from one Web Site to another.
Context
SCIM is a specification designed to reduce the complexity of user management operations by providing a common user schema and the patterns for exchanging such schema using HTTP in a platform-neutral fashion. The aim of SCIM is achieving interoperability, security, and scalability in the context of identity management.
Developers can think of SCIM merely as a REST API with endpoints exposing CRUD functionality (create, read, update and delete).
The standard is governed by the following IETF documents: RFC 7642, RFC 7643, and RFC 7644.
Clearly, this API must not be anonymously accessed. However, the basic SCIM standard does not define a specific mechanism to prevent unauthorized requests to endpoints. There are just a few guidelines in section 2 of RFC 7644 concerned with authentication and authorization.
Problems
Clearly, this API must not be anonymously accessed. However, the basic SCIM standard does not define a specific mechanism to prevent unauthorized requests to endpoints. There are just a few guidelines in section 2 of RFC 7644 concerned with authentication and authorization.
