RFC 7643: System for Cross-domain Identity Management: Core Schema
In plain English — editorial summary, not part of the RFC
The System for Cross-domain Identity Management (SCIM) specifications are designed to make identity management in cloud-based applications and services easier. The specification suite builds upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its 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 HTTP. This document provides a platform-neutral schema and extension model for representing users and groups and other resource types in JSON format. This schema is intended for exchange and use with cloud service providers.
Document record
- Document ID
- RFC7643
- Published
- September 2015
- Authors
- P. Hunt; K. Grizzle; E. Wahlstroem; C. Mortimore
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 104
- 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 8417Security Event Token (SET)Current
July 2018
- RFC 6806Kerberos Principal Name Canonicalization and Cross-Realm ReferralsCurrent
November 2012
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
- RFC 6030Portable Symmetric Key Container (PSKC)Current
October 2010
- RFC 9944Device Schema Extensions to the System for Cross-Domain Identity Management (SCIM) ModelCurrent
May 2026
- RFC 7458Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet CoreCurrent
February 2015
- RFC 7877Session Peering Provisioning Framework (SPPF)Current
August 2016
- RFC 7878Session Peering Provisioning (SPP) Protocol over SOAPCurrent
August 2016
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?