RFC 7644: System for Cross-domain Identity Management: Protocol
In plain English — editorial summary, not part of the RFC
The System for Cross-domain Identity Management (SCIM) specification is an HTTP-based protocol that makes managing identities in multi-domain scenarios easier to support via a standardized service. Examples include, but are not limited to, enterprise-to-cloud service providers and inter-cloud scenarios. The 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's intent is to reduce the cost and complexity of user management operations by providing a common user schema, an extension model, and a service protocol defined by this document.
Document record
- Document ID
- RFC7644
- Published
- September 2015
- Authors
- P. Hunt; K. Grizzle; M. Ansari; E. Wahlstroem; C. Mortimore
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 89
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7643System for Cross-domain Identity Management: Core SchemaUpdated
September 2015
- RFC 7642System for Cross-domain Identity Management: Definitions, Overview, Concepts, and RequirementsCurrent
September 2015
- RFC 7638JSON Web Key (JWK) ThumbprintCurrent
September 2015
- RFC 7636Proof Key for Code Exchange by OAuth Public ClientsCurrent
September 2015
- RFC 7634ChaCha20, Poly1305, and Their Use in the Internet Key Exchange Protocol (IKE) and IPsecCurrent
August 2015
- RFC 7632Endpoint Security Posture Assessment: Enterprise Use CasesCurrent
September 2015
- RFC 7628A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuthCurrent
August 2015
- RFC 7627Transport Layer Security (TLS) Session Hash and Extended Master Secret ExtensionObsoleted
September 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?