draft-ietf-scim-core-schema-09.txt   draft-ietf-scim-core-schema-10.txt 
Network Working Group K. Grizzle Network Working Group P. Hunt, Ed.
Internet-Draft SailPoint Internet-Draft Oracle
Intended status: Standards Track P. Hunt, Ed. Intended status: Standards Track K. Grizzle
Expires: March 2, 2015 Oracle Expires: March 19, 2015 SailPoint
E. Wahlstroem E. Wahlstroem
Nexus Technology Nexus Technology
C. Mortimore C. Mortimore
Salesforce Salesforce
August 29, 2014 September 15, 2014
System for Cross-Domain Identity Management: Core Schema System for Cross-Domain Identity Management: Core Schema
draft-ietf-scim-core-schema-09 draft-ietf-scim-core-schema-10
Abstract Abstract
The System for Cross-Domain Identity Management (SCIM) specifications The System for Cross-Domain Identity Management (SCIM) specifications
are designed to make identity management in cloud based applications are designed to make identity management in cloud based applications
and services easier. The specification suite builds upon experience and services easier. The specification suite builds upon experience
with existing schemas and deployments, placing specific emphasis on with existing schemas and deployments, placing specific emphasis on
simplicity of development and integration, while applying existing simplicity of development and integration, while applying existing
authentication, authorization, and privacy models. Its intent is to authentication, authorization, and privacy models. Its intent is to
reduce the cost and complexity of user management operations by reduce the cost and complexity of user management operations by
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 2, 2015. This Internet-Draft will expire on March 19, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction and Overview . . . . . . . . . . . . . . . . . . 3 1. Introduction and Overview . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Notation and Conventions . . . . . . . . . . 4 1.1. Requirements Notation and Conventions . . . . . . . . . . 4
1.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
2. SCIM Schema Structure . . . . . . . . . . . . . . . . . . . . 5 2. SCIM Schema Data Types . . . . . . . . . . . . . . . . . . . 5
2.1. Attribute Data Types . . . . . . . . . . . . . . . . . . 5 2.1. Attribute Data Types . . . . . . . . . . . . . . . . . . 5
2.1.1. String . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.1. String . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.2. Boolean . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.3. Decimal . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.3. Decimal . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.4. Integer . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.4. Integer . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.5. DateTime . . . . . . . . . . . . . . . . . . . . . . 6 2.1.5. DateTime . . . . . . . . . . . . . . . . . . . . . . 6
2.1.6. Binary . . . . . . . . . . . . . . . . . . . . . . . 7 2.1.6. Binary . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.7. Reference . . . . . . . . . . . . . . . . . . . . . . 7 2.1.7. Reference . . . . . . . . . . . . . . . . . . . . . . 7
2.1.8. Complex . . . . . . . . . . . . . . . . . . . . . . . 7 2.1.8. Complex . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. Multi-valued Attributes . . . . . . . . . . . . . . . . . 7 2.2. Multi-valued Attributes . . . . . . . . . . . . . . . . . 7
2.3. Unassigned and Null Values . . . . . . . . . . . . . . . 8 2.3. Unassigned and Null Values . . . . . . . . . . . . . . . 8
3. Schema Extension Model . . . . . . . . . . . . . . . . . . . 8 3. SCIM Resources . . . . . . . . . . . . . . . . . . . . . . . 8
3.1. Resource Type Extensions . . . . . . . . . . . . . . . . 8 3.1. Common Attributes . . . . . . . . . . . . . . . . . . . . 11
3.2. Attribute Extensions . . . . . . . . . . . . . . . . . . 9 3.2. Defining New Resource Types . . . . . . . . . . . . . . . 12
4. SCIM Core Schema . . . . . . . . . . . . . . . . . . . . . . 9 3.3. Attribute Extensions to Resources . . . . . . . . . . . . 12
4.1. Common Schema Attributes . . . . . . . . . . . . . . . . 9 4. SCIM Core Resources and Extensions . . . . . . . . . . . . . 13
4.2. "schemas" Attribute . . . . . . . . . . . . . . . . . . . 10 4.1. User Resource Schema . . . . . . . . . . . . . . . . . . 13
5. SCIM User Schema . . . . . . . . . . . . . . . . . . . . . . 11 4.1.1. Singular Attributes . . . . . . . . . . . . . . . . . 13
5.1. Singular Attributes . . . . . . . . . . . . . . . . . . . 11 4.1.2. Multi-valued Attributes . . . . . . . . . . . . . . . 16
5.2. Multi-valued Attributes . . . . . . . . . . . . . . . . . 13 4.2. Group Resource Schema . . . . . . . . . . . . . . . . . . 18
6. SCIM Enterprise User Schema Extension . . . . . . . . . . . . 16 4.3. Enterprise User Schema Extension . . . . . . . . . . . . 19
7. SCIM Group Schema . . . . . . . . . . . . . . . . . . . . . . 17 5. Service Provider Configuration Schema . . . . . . . . . . . . 19
8. Service Provider Configuration Schema . . . . . . . . . . . . 17 6. ResourceType Schema . . . . . . . . . . . . . . . . . . . . . 21
9. ResourceType Schema . . . . . . . . . . . . . . . . . . . . . 19 7. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 22
10. Schema Schema . . . . . . . . . . . . . . . . . . . . . . . . 20 8. JSON Representation . . . . . . . . . . . . . . . . . . . . . 25
11. JSON Representation . . . . . . . . . . . . . . . . . . . . . 23 8.1. Minimal User Representation . . . . . . . . . . . . . . . 25
11.1. Minimal User Representation . . . . . . . . . . . . . . 23 8.2. Full User Representation . . . . . . . . . . . . . . . . 26
11.2. Full User Representation . . . . . . . . . . . . . . . . 23 8.3. Enterprise User Extension Representation . . . . . . . . 29
11.3. Enterprise User Extension Representation . . . . . . . . 26 8.4. Group Representation . . . . . . . . . . . . . . . . . . 32
11.4. Group Representation . . . . . . . . . . . . . . . . . . 29 8.5. Service Provider Configuration Representation . . . . . . 33
11.5. Service Provider Configuration Representation . . . . . 30 8.6. Resource Type Representation . . . . . . . . . . . . . . 34
11.6. Resource Type Representation . . . . . . . . . . . . . . 31 8.7. Schema Representation . . . . . . . . . . . . . . . . . . 34
11.7. Schema Representation . . . . . . . . . . . . . . . . . 32 9. Security Considerations . . . . . . . . . . . . . . . . . . . 55
12. Security Considerations . . . . . . . . . . . . . . . . . . . 54 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 10.1. New Registration of SCIM URN Sub-namespace . . . . . . . 56
13.1. New Registration of SCIM URN Sub-namespace . . . . . . . 54 10.2. URN Sub-Namespace for SCIM . . . . . . . . . . . . . . . 56
13.2. URN Sub-Namespace for SCIM . . . . . . . . . . . . . . . 54 10.2.1. Specification Template . . . . . . . . . . . . . . . 57
13.2.1. Specification Template . . . . . . . . . . . . . . . 55 10.2.2. Pre-Registered SCIM Schema Identifiers . . . . . . . 59
13.2.2. Pre-Registered SCIM Schema Identifiers . . . . . . . 57 10.3. Registering SCIM Schemas . . . . . . . . . . . . . . . . 59
13.3. Registering SCIM Schemas . . . . . . . . . . . . . . . . 57 10.3.1. Registration Procedure . . . . . . . . . . . . . . . 59
13.3.1. Registration Procedure . . . . . . . . . . . . . . . 58 10.3.2. Schema Registration Template . . . . . . . . . . . . 60
13.3.2. Schema Registration Template . . . . . . . . . . . . 58 10.4. Initial SCIM Schema Registry . . . . . . . . . . . . . . 60
13.4. Initial SCIM Schema Registry . . . . . . . . . . . . . . 59 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 61
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 60 11.1. Normative References . . . . . . . . . . . . . . . . . . 61
14.1. Normative References . . . . . . . . . . . . . . . . . . 60 11.2. Informative References . . . . . . . . . . . . . . . . . 62
14.2. Informative References . . . . . . . . . . . . . . . . . 61 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 63
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 61 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 63
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 66
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 64
1. Introduction and Overview 1. Introduction and Overview
While there are existing standards for describing and exchanging user While there are existing standards for describing and exchanging user
information, many of these standards can be difficult to implement information, many of these standards can be difficult to implement
and/or use; e.g., their wire protocols do not easily traverse and/or use; e.g., their wire protocols do not easily traverse
firewalls and/or are not easily layered onto existing web protocols. firewalls and/or are not easily layered onto existing web protocols.
As a result, many cloud providers implement non-standardized As a result, many cloud providers implement non-standardized
protocols for managing users within their services. This increases protocols for managing users within their services. This increases
both the cost and complexity associated with organizations adopting both the cost and complexity associated with organizations adopting
skipping to change at page 4, line 32 skipping to change at page 4, line 29
Service Provider Service Provider
An HTTP web application that provides identity information via the An HTTP web application that provides identity information via the
SCIM protocol. SCIM protocol.
Client Client
A website or application that uses the SCIM protocol to manage A website or application that uses the SCIM protocol to manage
identity data maintained by the service provider. The client identity data maintained by the service provider. The client
initiates SCIM HTTP requests to a target service provider. initiates SCIM HTTP requests to a target service provider.
Resource
A service provider managed artifact containing one or more
attributes. For example a "User" or "Group".
Resource Type Resource Type
A type of a resource that is managed by a service provider. The A type of a resource that is managed by a service provider. The
resource type defines the resource name, endpoint URL, Schemas, resource type defines the resource name, endpoint URL, Schemas,
and other meta-data which indicate where a resource is managed and and other meta-data which indicate where a resource is managed and
how it is composed; e.g. "User" or "Group". how it is composed; e.g. "User" or "Group".
Resource
A service provider managed artifact containing one or more
attributes. For example a "User" or "Group".
Schema Schema
A collection of Attribute Definitions that describe the contents A collection of Attribute Definitions that describe the contents
of an entire or partial resource; e.g. of an entire or partial resource; e.g.
"urn:ietf:params:scim:schemas:core:2.0:User". "urn:ietf:params:scim:schemas:core:2.0:User".
Singular Attribute Singular Attribute
A resource attribute that contains 0..1 values; e.g. A resource attribute that contains 0..1 values; e.g.
"displayName". "displayName".
Multi-valued Attribute Multi-valued Attribute
skipping to change at page 5, line 16 skipping to change at page 5, line 14
A singular or multi-valued attribute whose value is a primitive; A singular or multi-valued attribute whose value is a primitive;
e.g. "String". e.g. "String".
Complex Attribute Complex Attribute
A singular or multi-valued attribute whose value is a composition A singular or multi-valued attribute whose value is a composition
of one or more simple attributes; e.g. "addresses". of one or more simple attributes; e.g. "addresses".
Sub-Attribute Sub-Attribute
A simple attribute contained within a complex attribute. A simple attribute contained within a complex attribute.
2. SCIM Schema Structure 2. SCIM Schema Data Types
SCIM schema provides a minimal core schema for representing users and SCIM schema provides a minimal core schema for representing users and
groups (resources), encompassing common attributes found in many groups (resources), encompassing common attributes found in many
existing deployments and schemas. In addition to the minimal core existing deployments and schemas. In addition to the minimal core
schema, this document also specifies a standardized means by which schema, this document also specifies a standardized means by which
service providers may extend schema to define new resources and service providers may extend schema to define new resources and
attributes in both standardized and service provider specific cases. attributes in both standardized and service provider specific cases.
Resources are categorized into common resource types such as "User" Resources are categorized into common resource types such as "User"
or "Group"). Collections of resources of the same type are usually or "Group"). Collections of resources of the same type are usually
skipping to change at page 5, line 38 skipping to change at page 5, line 36
A resource is a collection of attributes identified by one or more A resource is a collection of attributes identified by one or more
schemas. Minimally, an attribute consists of the attribute name and schemas. Minimally, an attribute consists of the attribute name and
at least one simple or complex value either of which may be multi- at least one simple or complex value either of which may be multi-
valued. For each attribute, SCIM schema defines the data type, valued. For each attribute, SCIM schema defines the data type,
plurality, mutability, and other distinguishing features of an plurality, mutability, and other distinguishing features of an
attribute. attribute.
Attribute names SHOULD be camel-cased (e.g. "camelCase"). SCIM Attribute names SHOULD be camel-cased (e.g. "camelCase"). SCIM
resources are represented in JSON [RFC7159] and MUST specify schema resources are represented in JSON [RFC7159] and MUST specify schema
via the "schemas" attribute per Section 4.2. via the "schemas" attribute per Section 3.
Attribute names MUST conform to the following ABNF [RFC5234] rules: Attribute names MUST conform to the following ABNF [RFC5234] rules:
ATTRNAME = ALPHA *(nameChar) ATTRNAME = ALPHA *(nameChar)
nameChar = "-" / "_" / DIGIT / ALPHA nameChar = "-" / "_" / DIGIT / ALPHA
Figure 1: ABNF for Attribute Names Figure 1: ABNF for Attribute Names
2.1. Attribute Data Types 2.1. Attribute Data Types
Attribute data types are derived from JSON [RFC7159] and unless Attribute data types are derived from JSON [RFC7159] and unless
otherwise specified have the following characteristics (see otherwise specified have the following characteristics (see Section 7
Section 10 for attribute characteristic definitions): for attribute characteristic definitions):
o are optional (is not required). o are optional (is not required).
o are case insensitive (caseExact=false), o are case insensitive (caseExact=false),
o are modifiable (mutability is readWrite), o are modifiable (mutability is readWrite),
o are returned in response to queries (returned by default), o are returned in response to queries (returned by default),
o are not unique (uniqueness=none), and, o are not unique (uniqueness=none), and,
skipping to change at page 8, line 37 skipping to change at page 8, line 34
2.3. Unassigned and Null Values 2.3. Unassigned and Null Values
Unassigned attributes, the null value, or empty array (in the case of Unassigned attributes, the null value, or empty array (in the case of
a multi-valued attribute) SHALL be considered to be equivalent in a multi-valued attribute) SHALL be considered to be equivalent in
"state". Assigning an attribute with the value "null" or an empty "state". Assigning an attribute with the value "null" or an empty
array (in the case of multi-valued attributes) has the effect of array (in the case of multi-valued attributes) has the effect of
making the attribute "unassigned". When a resource is expressed in making the attribute "unassigned". When a resource is expressed in
JSON form, unassigned attributes, though they are defined in schema, JSON form, unassigned attributes, though they are defined in schema,
MAY be omitted for compactness. MAY be omitted for compactness.
3. Schema Extension Model 3. SCIM Resources
SCIM supports two types of extensions: Resource Types and Attribute Each SCIM resource is a JSON object that has the following
extensions. New resources allow new objects to be defined, while components:
attribute extensions allow for new classes of attributes to be added
to an existing resource type. For example, the enterprise user
extension defines additional attributes for a "User" resource type.
3.1. Resource Type Extensions Resource Type
Each resource (or JSON object) in SCIM has a resource type
("meta.resourceType") that defines the resource's core attribute
schema and any attribute extension schema as well as the endpoint
where objects of the same type may be found. More information
about a resource MAY be found in its resourceType definition (see
Section 6).
Each resource type supported by a SCIM service provider defines the Schemas Attribute
types name, endpoint, base schema (the attributes), and any schema The "schemas" attribute is a REQUIRED attribute that MUST be
extensions registered for use with the resource type. In order to present and is an array of Strings containing URIs which are used
offer new types of resources, a service provider defines the new to indicate the namespace of SCIM schema that defines the
resource type as specified in Section 9. attributes present in the current JSON structure. It may be used
by parsers to define the attributes present in the JSON structure
that is the body to an HTTP Request or Response. Each String
value must be a unique URI. All representations of SCIM schema
MUST include a non-zero value array with value(s) of the URIs
supported by that representation. The schemas attribute for a
resource MUST only contain values defined as "schema" and
"schemaExtensions" for the resource's "resourceType". Duplicate
values MUST NOT be included. Value order is not specified and
MUST not impact behavior.
3.2. Attribute Extensions Common Attributes
Are attributes that are part of every SCIM resource regardless of
the value of the "schemas" attribute present in a JSON body.
These attributes are not defined in any particular schema, but
SHALL be assumed to be present in every resource regardless of the
value of the "schemas" attribute. See Section 3.1.
SCIM allows resource types to have extensions in addition to their Core Attributes
core schema. This is similar to how "ObjectClasses" used in LDAP. A resource's core attributes are those attributes that sit at the
However, unlike LDAP there is no inheritance model; all extensions top level of the JSON object together with the common attributes
are additive (similar to LDAP Auxiliary Object Class [RFC4512] ). (such as the resource "id"). The list of valid attributes is
Each "schemas" value indicates additive schema that may exist in a specified by the resource's resource type "schema" attribute (see
SCIM resource representation. The "schemas" attribute MUST contain Section 6). This same value is also present in the resource's
at least one value which SHALL be the base schema for the resource. "schemas" attribute.
The "schemas" attribute MAY contain additional values indicating
extended schemas that are in use. Schema extensions SHOULD avoid
redefining any attributes defined in this specification and SHOULD
follow conventions defined in this specification. Except for the
base object schema, the schema extension URI SHALL be used as a JSON
container to distinguish attributes belonging to the extension
namespace from base schema attributes. See Figure 4 for an example
JSON representation of an extended User.
In order to determine which "schemas" URI value is the base schema Extended Attributes
and which is extended schema for any given resource, the resource's Extended schema attributes are specified by the resource's
"resourceType" attribute value MAY be used to retrieve the resource's resource type "schemaExtensions" attribute (see Section 6).
"ResourceType" schema ( Section 9 ). See example "ResourceType" Unlike core attributes, extended attributes are kept in their own
representation in Figure 7. sub-attribute namespace identified by the schema extension URI.
This avoids attribute name conflicts that may arise due to
conflicts from separate schema extensions.
4. SCIM Core Schema The following example "User" contains the common attributes "id",
"externalId", and the complex attribute "meta" which contains the
sub-attribute "resourceType". The resource also contains core
attributes "userName", "name", as well as extended enterprise user
attributes "employeeNumber" and "costCenter" which are contained in
their own JSON sub-structure identified by their schema URI. Some
values have been omitted (...), shortened or spaced out for clarity.
4.1. Common Schema Attributes {
"schemas":
[ "urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
"id": "2819c223-7f76-453a-413861904646",
"externalId": ["701984"],
"userName": "bjensen@example.com",
"name": {
"formatted": "Ms. Barbara J Jensen III",
"familyName": "Jensen",
"givenName": "Barbara",
"middleName": "Jane",
"honorificPrefix": "Ms.",
"honorificSuffix": "III"
},
...
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"employeeNumber": "701984",
"costCenter": "4130",
...
},
"meta": {
"resourceType": "User",
"created": "2010-01-23T04:56:22Z",
"lastModified": "2011-05-13T04:42:34Z",
"version": "W\/\"3694e05e9dff591\"",
"location": "https://example.com/v2/Users/2819c223-7f76-453a-413861904646"
}
}
Figure 2: Example JSON Resource Structure
3.1. Common Attributes
Each SCIM resource (Users, Groups, etc.) includes the following Each SCIM resource (Users, Groups, etc.) includes the following
common attributes. With the exception of "ServiceProviderConfig" and common attributes. With the exception of "ServiceProviderConfig" and
"ResourceType" server discovery endpoints and their associated "ResourceType" server discovery endpoints and their associated
resources, these attributes MUST be included in all resources, resources, these attributes MUST be included in all resources,
including any extended resource types. Common attributes are including any extended resource types. Common attributes are
considered to be part of every base resource schema and do not use considered to be part of every base resource schema and do not use
their own schemas URI and SHALL not be considered schema extensions. their own schemas URI and SHALL not be considered schema extensions.
For backwards compatibility reasons, some existing schema MAY list
common attributes as part of the schema. The attribute
characteristics listed here SHALL take precedence.
id id
A unique identifier for a SCIM resource as defined by the service A unique identifier for a SCIM resource as defined by the service
provider. Each representation of the resource MUST include a non- provider. Each representation of the resource MUST include a non-
empty "id" value. This identifier MUST be unique across the SCIM empty "id" value. This identifier MUST be unique across the SCIM
service provider's entire set of resources. It MUST be a stable, service provider's entire set of resources. It MUST be a stable,
non-reassignable identifier that does not change when the same non-reassignable identifier that does not change when the same
resource is returned in subsequent requests. The value of the resource is returned in subsequent requests. The value of the
"id" attribute is always issued by the service provider and MUST "id" attribute is always issued by the service provider and MUST
NOT be specified by the client. The string "bulkId" is a reserved NOT be specified by the client. The string "bulkId" is a reserved
keyword and MUST NOT be used within any unique identifier value. keyword and MUST NOT be used within any unique identifier value.
REQUIRED and has a mutability of "readOnly". REQUIRED and has a mutability of "readOnly". See Section 9 for
additional considerations regarding privacy.
externalId externalId
An identifier for the resource as defined by the client. The A String that is an identifier for the resource as defined by the
"externalId" may simplify identification of the resource between client. The "externalId" may simplify identification of the
client and service provider by allowing the client to use a filter resource between client and service provider by allowing the
to locate the resource with its own identifier, obviating the need client to use a filter to locate the resource with its own
to store a local mapping between the local identifier of the identifier, obviating the need to store a local mapping between
resource and the identifier used by the service provider. Each the local identifier of the resource and the identifier used by
resource MAY include a non-empty "externalId" value. The value of the service provider. Each resource MAY include a non-empty
the "externalId" attribute is always issued by the client and can "externalId" value. The value of the "externalId" attribute is
never be specified by the service provider. The service provider always issued by the client and MUST NOT be specified by the
MUST always interpret the externalId as scoped to the client's service provider. The service provider MUST always interpret the
tenant. externalId as scoped to the client's tenant. While the server
does not enforce uniqueness, it is assumed that the value's
uniqueness is controlled by the client setting the value. See
Section 9 for additional considerations regarding privacy.
meta meta
A complex attribute containing resource metadata. All sub- A complex attribute containing resource metadata. All sub-
attributes are OPTIONAL attributes are OPTIONAL and are asserted by the Service Provider:
resourceType The name of the resource type of the resource. This resourceType The name of the resource type of the resource. This
attribute has mutability of "readOnly". attribute has mutability of "readOnly".
created The DateTime the resource was added to the service created The DateTime the resource was added to the service
provider. The attribute MUST be a DateTime. This attribute provider. The attribute MUST be a DateTime. This attribute
has mutability of "readOnly". has mutability of "readOnly".
lastModified The most recent DateTime the details of this lastModified The most recent DateTime the details of this
resource were updated at the service provider. If this resource were updated at the service provider. If this
skipping to change at page 10, line 43 skipping to change at page 12, line 26
attribute MUST be a DateTime and has mutability of "readOnly". attribute MUST be a DateTime and has mutability of "readOnly".
location The URI of the resource being returned. This value MUST location The URI of the resource being returned. This value MUST
be the same as the Location HTTP response header. The be the same as the Location HTTP response header. The
attribute has mutability of "readOnly". attribute has mutability of "readOnly".
version The version of the resource being returned. This value version The version of the resource being returned. This value
must be the same as the ETag HTTP response header. The must be the same as the ETag HTTP response header. The
attribute has mutability of "readOnly". attribute has mutability of "readOnly".
4.2. "schemas" Attribute 3.2. Defining New Resource Types
The "schemas" attribute is a REQUIRED attribute and is an array of SCIM may be extended to define new classes of resources by defining a
Strings containing URIs which are used to indicate the namespace of resource type. Each resource type defines the name, endpoint, base
SCIM schema as well as any schema extensions that together defines schema (the attributes), and any schema extensions registered for use
the attributes in a resource. Each String value must be a unique with the resource type. In order to offer new types of resources, a
URI. All representations of SCIM schema MUST include a non-zero service provider defines the new resource type as specified in
value array with value(s) of the URIs supported by that Section 6and defines a schema representation (see Section 8.7).
representation. The schemas attribute for a resource MUST only
contain values defined as "schema" and "schemaExtensions" for the
resource's "resourceType". Duplicate values MUST NOT be included.
Value order is not specified and MUST not impact behavior.
5. SCIM User Schema 3.3. Attribute Extensions to Resources
SCIM allows resource types to have extensions in addition to their
core schema. This is similar to how "ObjectClasses" used in LDAP.
However, unlike LDAP there is no inheritance model; all extensions
are additive (similar to LDAP Auxiliary Object Class [RFC4512] ).
Each "schemas" value indicates additive schema that may exist in a
SCIM resource representation. The "schemas" attribute MUST contain
at least one value which SHALL be the base schema for the resource.
The "schemas" attribute MAY contain additional values indicating
extended schemas that are in use. Schema extensions SHOULD avoid
redefining any attributes defined in this specification and SHOULD
follow conventions defined in this specification. Except for the
base object schema, the schema extension URI SHALL be used as a JSON
container to distinguish attributes belonging to the extension
namespace from base schema attributes. See Figure 5 for an example
JSON representation of an extended User.
In order to determine which "schemas" URI value is the base schema
and which is extended schema for any given resource, the resource's
"resourceType" attribute value MAY be used to retrieve the resource's
"ResourceType" schema ( Section 6 ). See example "ResourceType"
representation in Figure 8.
4. SCIM Core Resources and Extensions
This section defines the default resources schemas present in a SCIM
server. SCIM is not exclusive to these resources, and may be
extended to support other resource types (see Section 3.2).
4.1. User Resource Schema
SCIM provides a resource type for "User" resources. The core schema SCIM provides a resource type for "User" resources. The core schema
for "User" is identified using the URI: for "User" is identified using the URI:
"urn:ietf:params:scim:schemas:core:2.0:User". The following "urn:ietf:params:scim:schemas:core:2.0:User". The following
attributes are defined in addition to the core schema attributes: attributes are defined in addition to the core schema attributes:
5.1. Singular Attributes 4.1.1. Singular Attributes
userName userName
A service provider unique identifier for the user, typically used A service provider unique identifier for the user, typically used
by the user to directly authenticate to the service provider. by the user to directly authenticate to the service provider.
Often displayed to the user as their unique identifier within the Often displayed to the user as their unique identifier within the
system (as opposed to id or externalId, which are generally opaque system (as opposed to "id" or "externalId", which are generally
and not user-friendly identifiers). Each User MUST include a non- opaque and not user-friendly identifiers). Each User MUST include
empty userName value. This identifier MUST be unique across the a non-empty userName value. This identifier MUST be unique across
service provider's entire set of Users. RECOMMENDED. the service provider's entire set of Users. RECOMMENDED.
name name
The components of the user's real name. Service providers MAY The components of the user's real name. Service providers MAY
return just the full name as a single string in the formatted sub- return just the full name as a single string in the formatted sub-
attribute, or they MAY return just the individual component attribute, or they MAY return just the individual component
attributes using the other sub-attributes, or they MAY return attributes using the other sub-attributes, or they MAY return
both. If both variants are returned, they SHOULD be describing both. If both variants are returned, they SHOULD be describing
the same name, with the formatted name indicating how the the same name, with the formatted name indicating how the
component attributes should be combined. component attributes should be combined.
skipping to change at page 13, line 43 skipping to change at page 16, line 7
password password
The user's clear text password. This attribute is intended to be The user's clear text password. This attribute is intended to be
used as a means to specify an initial password when creating a new used as a means to specify an initial password when creating a new
User or to reset an existing User's password. Password policies User or to reset an existing User's password. Password policies
and the ability to update or set passwords are out of scope of and the ability to update or set passwords are out of scope of
this document. The mutability of this attribute is "writeOnly" this document. The mutability of this attribute is "writeOnly"
indicating the value MUST NOT be returned by a service provider in indicating the value MUST NOT be returned by a service provider in
any form. any form.
5.2. Multi-valued Attributes 4.1.2. Multi-valued Attributes
The following multi-valued attributes are defined. The following multi-valued attributes are defined.
emails emails
E-mail addresses for the User. The value SHOULD be canonicalized E-mail addresses for the User. The value SHOULD be canonicalized
by the service provider, e.g. "bjensen@example.com" instead of by the service provider, e.g. "bjensen@example.com" instead of
"bjensen@EXAMPLE.COM". Canonical type values of "work", "home", "bjensen@EXAMPLE.COM". Canonical type values of "work", "home",
and "other". and "other".
phoneNumbers phoneNumbers
Phone numbers for the user. The value SHOULD be canonicalized by Phone numbers for the user. The value SHOULD be canonicalized by
the service provider according to format in [RFC3966] e.g. the service provider according to format in [RFC3966] e.g.
'tel:+1-201-555-0123'. Canonical type values of "work", "home", 'tel:+1-201-555-0123'. Canonical type values of "work", "home",
"mobile", "fax", "pager", and "other". "mobile", "fax", "pager", and "other".
ims ims
skipping to change at page 14, line 44 skipping to change at page 17, line 9
addresses addresses
A physical mailing address for this user. Canonical type values A physical mailing address for this user. Canonical type values
of "work", "home", and "other". The value attribute is a complex of "work", "home", and "other". The value attribute is a complex
type with the following sub-attributes. All sub-attributes are type with the following sub-attributes. All sub-attributes are
OPTIONAL. OPTIONAL.
formatted The full mailing address, formatted for display or use formatted The full mailing address, formatted for display or use
with a mailing label. This attribute MAY contain newlines. with a mailing label. This attribute MAY contain newlines.
streetAddress The full street address component, which may streetAddress The full street address component, which may
include house number, street name, P.O. box, and multi-line include house number, street name, P.O. box, and multi-line
extended street address information. This attribute MAY extended street address information. This attribute MAY
contain newlines. contain newlines.
locality The city or locality component. locality The city or locality component.
region The state or region component. region The state or region component.
postalCode The zipcode or postal code component. postalCode The zipcode or postal code component.
country The country name component. When specified the value country The country name component. When specified the value
skipping to change at page 15, line 31 skipping to change at page 17, line 45
that clients may modify membership through the "Group" resource. that clients may modify membership through the "Group" resource.
Indirect membership indicates user membership is transitive or Indirect membership indicates user membership is transitive or
dynamic and implies that clients cannot modify indirect group dynamic and implies that clients cannot modify indirect group
membership through the "Group" resource but MAY modify direct membership through the "Group" resource but MAY modify direct
group membership through the "Group" resource which MAY influence group membership through the "Group" resource which MAY influence
indirect memberships. If the SCIM service provider exposes a indirect memberships. If the SCIM service provider exposes a
Group resource, the "value" sub-attribute MUST be the "id" and the Group resource, the "value" sub-attribute MUST be the "id" and the
"$ref" sub-attribute must be the URI of the corresponding "Group" "$ref" sub-attribute must be the URI of the corresponding "Group"
resources to which the user belongs. Since this attribute has a resources to which the user belongs. Since this attribute has a
mutability of "readOnly", group membership changes MUST be applied mutability of "readOnly", group membership changes MUST be applied
via the Group Resource (Section 7). The attribute has a via the Group Resource (Section 4.2). The attribute has a
mutability of "readOnly". mutability of "readOnly".
entitlements entitlements
A list of entitlements for the user that represent a thing the A list of entitlements for the user that represent a thing the
user has. An entitlement MAY be an additional right to a thing, user has. An entitlement MAY be an additional right to a thing,
object, or service. No vocabulary or syntax is specified and object, or service. No vocabulary or syntax is specified and
service providers and clients are expected to encode sufficient service providers and clients are expected to encode sufficient
information in the value so as to accurately and without ambiguity information in the value so as to accurately and without ambiguity
determine what the user has access to. This value has NO determine what the user has access to. This value has NO
canonical types though type may be useful as a means to scope canonical types though type may be useful as a means to scope
skipping to change at page 16, line 8 skipping to change at page 18, line 21
user is; e.g., "Student, Faculty". No vocabulary or syntax is user is; e.g., "Student, Faculty". No vocabulary or syntax is
specified though it is expected that a role value is a String or specified though it is expected that a role value is a String or
label representing a collection of entitlements. This value has label representing a collection of entitlements. This value has
NO canonical types. NO canonical types.
x509Certificates x509Certificates
A list of certificates issued to the User. Values are Binary A list of certificates issued to the User. Values are Binary
(Section 2.1.6) and DER encoded x509. This value has NO canonical (Section 2.1.6) and DER encoded x509. This value has NO canonical
types. types.
6. SCIM Enterprise User Schema Extension 4.2. Group Resource Schema
SCIM provides a schema for representing groups, identified using the
following schema URI: "urn:ietf:params:scim:schemas:core:2.0:Group".
Group resources are meant to enable expression of common group or
role based access control models, although no explicit authorization
model is defined. It is intended that the semantics of group
membership and any behavior or authorization granted as a result of
membership are defined by the service provider are considered out of
scope for this specification.
The following singular attribute is defined in addition to the common
attributes defined in SCIM core schema:
displayName
A human readable name for the Group. REQUIRED.
The following multi-valued attribute is defined in addition to the
common attributes defined in SCIM Core Schema:
members
A list of members of the Group. While values MAY be added or
removed, sub-attributes of members are "immutable". The "value"
sub-attribute must be the "id" and the "$ref" sub-attribute must
be the URI of a SCIM resource, either a "User", or a "Group". The
intention of the "Group" type is to allow the service provider to
support nested groups. Service providers MAY require clients to
provide a non-empty members value based on the "required" sub
attribute of the "members" attribute in the "Group" resource
schema.
4.3. Enterprise User Schema Extension
The following SCIM extension defines attributes commonly used in The following SCIM extension defines attributes commonly used in
representing users that belong to, or act on behalf of a business or representing users that belong to, or act on behalf of a business or
enterprise. The enterprise user extension is identified using the enterprise. The enterprise user extension is identified using the
following schema URI: following schema URI:
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User". "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User".
The following Singular Attributes are defined: The following Singular Attributes are defined:
employeeNumber employeeNumber
skipping to change at page 17, line 5 skipping to change at page 19, line 45
value The "id" of the SCIM resource representing the user's value The "id" of the SCIM resource representing the user's
manager. RECOMMENDED. manager. RECOMMENDED.
$ref The URI of the SCIM resource representing the User's $ref The URI of the SCIM resource representing the User's
manager. RECOMMENDED. manager. RECOMMENDED.
displayName The displayName of the user's manager. This displayName The displayName of the user's manager. This
attribute is OPTIONAL and mutability is "readOnly". attribute is OPTIONAL and mutability is "readOnly".
7. SCIM Group Schema 5. Service Provider Configuration Schema
SCIM provides a schema for representing groups, identified using the
following schema URI: "urn:ietf:params:scim:schemas:core:2.0:Group".
Group resources are meant to enable expression of common group or
role based access control models, although no explicit authorization
model is defined. It is intended that the semantics of group
membership and any behavior or authorization granted as a result of
membership are defined by the service provider are considered out of
scope for this specification.
The following singular attribute is defined in addition to the common
attributes defined in SCIM core schema:
displayName
A human readable name for the Group. REQUIRED.
The following multi-valued attribute is defined in addition to the
common attributes defined in SCIM Core Schema:
members
A list of members of the Group. While values MAY be added or
removed, sub-attributes of members are "immutable". The "value"
sub-attribute must be the "id" and the "$ref" sub-attribute must
be the URI of a SCIM resource, either a "User", or a "Group". The
intention of the "Group" type is to allow the service provider to
support nested groups. Service providers MAY require clients to
provide a non-empty members value based on the "required" sub
attribute of the "members" attribute in the "Group" resource
schema.
8. Service Provider Configuration Schema
SCIM provides a schema for representing the service provider's SCIM provides a schema for representing the service provider's
configuration identified using the following schema URI: configuration identified using the following schema URI:
"urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig" "urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig"
The service provider configuration resource enables a service The service provider configuration resource enables a service
provider to discovery of SCIM specification features in a provider to discovery of SCIM specification features in a
standardized form as well as provide additional implementation standardized form as well as provide additional implementation
details to clients. All attributes are READ-ONLY (a mutability of details to clients. All attributes are READ-ONLY (a mutability of
"readOnly" ). Unlike other core resources, the "id" attribute is not "readOnly" ). Unlike other core resources, the "id" attribute is not
skipping to change at page 19, line 35 skipping to change at page 21, line 44
description A description of the Authentication Scheme. description A description of the Authentication Scheme.
REQUIRED. REQUIRED.
specUrl A HTTP addressable URL pointing to the Authentication specUrl A HTTP addressable URL pointing to the Authentication
Scheme's specification. OPTIONAL. Scheme's specification. OPTIONAL.
documentationUrl A HTTP addressable URL pointing to the documentationUrl A HTTP addressable URL pointing to the
Authentication Scheme's usage documentation. OPTIONAL. Authentication Scheme's usage documentation. OPTIONAL.
9. ResourceType Schema 6. ResourceType Schema
The "ResourceType" schema specifies the meta-data about a resource The "ResourceType" schema specifies the meta-data about a resource
type. Resource type resources are READ-ONLY and identified using the type. Resource type resources are READ-ONLY and identified using the
following schema URI: following schema URI:
"urn:ietf:params:scim:schemas:core:2.0:ResourceType". Unlike other "urn:ietf:params:scim:schemas:core:2.0:ResourceType". Unlike other
core resources, all attributes are REQUIRED unless otherwise core resources, all attributes are REQUIRED unless otherwise
specified. The "id" attribute is not required for the resource type specified. The "id" attribute is not required for the resource type
resource. resource.
The following Singular Attributes are defined: The following Singular Attributes are defined:
skipping to change at page 20, line 38 skipping to change at page 22, line 46
This MUST be equal to the "id" attribute of a "Schema" This MUST be equal to the "id" attribute of a "Schema"
resource. REQUIRED. resource. REQUIRED.
required A Boolean value that specifies whether the schema required A Boolean value that specifies whether the schema
extension is required for the resource type. If true, a extension is required for the resource type. If true, a
resource of this type MUST include this schema extension and resource of this type MUST include this schema extension and
include any attributes declared as required in this schema include any attributes declared as required in this schema
extension. If false, a resource of this type MAY omit this extension. If false, a resource of this type MAY omit this
schema extension. REQUIRED. schema extension. REQUIRED.
10. Schema Schema 7. Schema Definition
The "Schema" schema specifies the attribute(s) and meta-data that This section defines a way to specify the schema in use by resources
constitute a "Schema" resource. Schema resources have mutability of available and accepted by a SCIM service provider. For each
"readOnly" and identified using the following URI: "schemas" URI value, this schema specifies the defined attribute(s)
and their characteristics (mutability, returnability, etc). For
every schema URI used in a resource object, there is a corresponding
"Schema" resource. "Schema" resources have mutability of "readOnly"
and are identified using the following schema URI:
urn:ietf:params:scim:schemas:core:2.0:Schema urn:ietf:params:scim:schemas:core:2.0:Schema
Unlike other core resources the "Schema" resource MAY contain a Unlike other core resources the "Schema" resource MAY contain a
complex object within a sub-attribute and all attributes are REQUIRED complex object within a sub-attribute and all attributes are REQUIRED
unless otherwise specified. unless otherwise specified.
The following Singular Attributes are defined: The following Singular Attributes are defined:
id The unique URI of the schema. When applicable service providers id
The unique URI of the schema. When applicable service providers
MUST specify the URI specified in the core schema specification; MUST specify the URI specified in the core schema specification;
e.g., "urn:ietf:params:scim:schemas:core:2.0:User". Unlike most e.g., "urn:ietf:params:scim:schemas:core:2.0:User". Unlike most
other schemas, which use some sort of a GUID for the "id", the other schemas, which use some sort of a GUID for the "id", the
schema "id" is a URI so that it can be registered and is portable schema "id" is a URI so that it can be registered and is portable
between different service providers and clients. between different service providers and clients.
name The schema's human readable name. When applicable service name
The schema's human readable name. When applicable service
providers MUST specify the name specified in the core schema providers MUST specify the name specified in the core schema
specification; e.g., "User" or "Group". OPTIONAL. specification; e.g., "User" or "Group". OPTIONAL.
description The schema's human readable description. When description
applicable service providers MUST specify the description The schema's human readable description. When applicable service
specified in the core schema specification. OPTIONAL. providers MUST specify the description specified in the core
schema specification. OPTIONAL.
The following multi-valued attribute is defined: The following multi-valued attribute is defined:
attributes attributes
A complex type with the following set of sub-attributes that A complex type with the following set of sub-attributes that
defines service provider attributes and their qualities: defines service provider attributes and their qualities:
name The attribute's name. name The attribute's name.
type The attribute's data type; e.g., "String". type The attribute's data type; e.g., "String".
skipping to change at page 23, line 22 skipping to change at page 25, line 37
server SHOULD possess the same value. server SHOULD possess the same value.
global The value SHOULD be globally unique (e.g. an email global The value SHOULD be globally unique (e.g. an email
address, a GUID, or other value). No two resources on any address, a GUID, or other value). No two resources on any
server SHOULD possess the same value. server SHOULD possess the same value.
referenceTypes The names of the resource types that may be referenceTypes The names of the resource types that may be
referenced; e.g., "User". This is only applicable for referenced; e.g., "User". This is only applicable for
attributes that are of the "reference" Section 2.1.7 data type. attributes that are of the "reference" Section 2.1.7 data type.
11. JSON Representation 8. JSON Representation
11.1. Minimal User Representation 8.1. Minimal User Representation
The following is a non-normative example of the minimal required SCIM The following is a non-normative example of the minimal required SCIM
representation in JSON format. representation in JSON format.
{ {
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"], "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"id": "2819c223-7f76-453a-919d-413861904646", "id": "2819c223-7f76-453a-919d-413861904646",
"userName": "bjensen@example.com", "userName": "bjensen@example.com",
"meta": { "meta": {
"resourceType": "User", "resourceType": "User",
"created": "2010-01-23T04:56:22Z", "created": "2010-01-23T04:56:22Z",
"lastModified": "2011-05-13T04:42:34Z", "lastModified": "2011-05-13T04:42:34Z",
"version": "W\/\"3694e05e9dff590\"", "version": "W\/\"3694e05e9dff590\"",
"location": "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646" "location": "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646"
} }
} }
Figure 2: Example Minimal User JSON Representation Figure 3: Example Minimal User JSON Representation
11.2. Full User Representation 8.2. Full User Representation
The following is a non-normative example of the fully populated SCIM The following is a non-normative example of the fully populated SCIM
representation in JSON format. representation in JSON format.
{ {
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"], "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"id": "2819c223-7f76-453a-919d-413861904646", "id": "2819c223-7f76-453a-919d-413861904646",
"externalId": "701984", "externalId": ["701984"],
"userName": "bjensen@example.com", "userName": "bjensen@example.com",
"name": { "name": {
"formatted": "Ms. Barbara J Jensen III", "formatted": "Ms. Barbara J Jensen III",
"familyName": "Jensen", "familyName": "Jensen",
"givenName": "Barbara", "givenName": "Barbara",
"middleName": "Jane", "middleName": "Jane",
"honorificPrefix": "Ms.", "honorificPrefix": "Ms.",
"honorificSuffix": "III" "honorificSuffix": "III"
}, },
"displayName": "Babs Jensen", "displayName": "Babs Jensen",
skipping to change at page 26, line 33 skipping to change at page 29, line 9
], ],
"meta": { "meta": {
"resourceType": "User", "resourceType": "User",
"created": "2010-01-23T04:56:22Z", "created": "2010-01-23T04:56:22Z",
"lastModified": "2011-05-13T04:42:34Z", "lastModified": "2011-05-13T04:42:34Z",
"version": "W\/\"a330bc54f0671c9\"", "version": "W\/\"a330bc54f0671c9\"",
"location": "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646" "location": "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646"
} }
} }
Figure 3: Example Full User JSON Representation Figure 4: Example Full User JSON Representation
11.3. Enterprise User Extension Representation 8.3. Enterprise User Extension Representation
The following is a non-normative example of the fully populated User The following is a non-normative example of the fully populated User
using the enterprise User extension in JSON format. using the enterprise User extension in JSON format.
{ {
"schemas": "schemas":
[ "urn:ietf:params:scim:schemas:core:2.0:User", [ "urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"], "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
"id": "2819c223-7f76-453a-919d-413861904646", "id": "2819c223-7f76-453a-919d-413861904646",
"externalId": "701984", "externalId": ["701984"],
"userName": "bjensen@example.com", "userName": "bjensen@example.com",
"name": { "name": {
"formatted": "Ms. Barbara J Jensen III", "formatted": "Ms. Barbara J Jensen III",
"familyName": "Jensen", "familyName": "Jensen",
"givenName": "Barbara", "givenName": "Barbara",
"middleName": "Jane", "middleName": "Jane",
"honorificPrefix": "Ms.", "honorificPrefix": "Ms.",
"honorificSuffix": "III" "honorificSuffix": "III"
}, },
"displayName": "Babs Jensen", "displayName": "Babs Jensen",
skipping to change at page 29, line 39 skipping to change at page 32, line 16
}, },
"meta": { "meta": {
"resourceType": "User", "resourceType": "User",
"created": "2010-01-23T04:56:22Z", "created": "2010-01-23T04:56:22Z",
"lastModified": "2011-05-13T04:42:34Z", "lastModified": "2011-05-13T04:42:34Z",
"version": "W\/\"3694e05e9dff591\"", "version": "W\/\"3694e05e9dff591\"",
"location": "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646" "location": "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646"
} }
} }
Figure 4: Example Enterprise User JSON Representation Figure 5: Example Enterprise User JSON Representation
11.4. Group Representation 8.4. Group Representation
The following is a non-normative example of SCIM Group representation The following is a non-normative example of SCIM Group representation
in JSON format. in JSON format.
{ {
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:Group"], "schemas": ["urn:ietf:params:scim:schemas:core:2.0:Group"],
"id": "e9e30dba-f08f-4109-8486-d5c6a331660a", "id": "e9e30dba-f08f-4109-8486-d5c6a331660a",
"displayName": "Tour Guides", "displayName": "Tour Guides",
"members": [ "members": [
{ {
skipping to change at page 30, line 30 skipping to change at page 32, line 48
], ],
"meta": { "meta": {
"resourceType": "Group", "resourceType": "Group",
"created": "2010-01-23T04:56:22Z", "created": "2010-01-23T04:56:22Z",
"lastModified": "2011-05-13T04:42:34Z", "lastModified": "2011-05-13T04:42:34Z",
"version": "W\/\"3694e05e9dff592\"", "version": "W\/\"3694e05e9dff592\"",
"location": "https://example.com/v2/Groups/e9e30dba-f08f-4109-8486-d5c6a331660a" "location": "https://example.com/v2/Groups/e9e30dba-f08f-4109-8486-d5c6a331660a"
} }
} }
Figure 5: Example Group JSON Representation Figure 6: Example Group JSON Representation
11.5. Service Provider Configuration Representation 8.5. Service Provider Configuration Representation
The following is a non-normative example of the SCIM service provider The following is a non-normative example of the SCIM service provider
configuration representation in JSON format. configuration representation in JSON format.
{ {
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig"], "schemas": ["urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig"],
"documentationUrl":"http://example.com/help/scim.html", "documentationUrl":"http://example.com/help/scim.html",
"patch": { "patch": {
"supported":true "supported":true
}, },
skipping to change at page 31, line 38 skipping to change at page 34, line 11
], ],
"meta": { "meta": {
"location":"https://example.com/v2/ServiceProviderConfig", "location":"https://example.com/v2/ServiceProviderConfig",
"resourceType": "ServiceProviderConfig", "resourceType": "ServiceProviderConfig",
"created": "2010-01-23T04:56:22Z", "created": "2010-01-23T04:56:22Z",
"lastModified": "2011-05-13T04:42:34Z", "lastModified": "2011-05-13T04:42:34Z",
"version": "W\/\"3694e05e9dff594\"" "version": "W\/\"3694e05e9dff594\""
} }
} }
Figure 6: Example Service Provider Config JSON Representation Figure 7: Example Service Provider Config JSON Representation
11.6. Resource Type Representation 8.6. Resource Type Representation
The following is a non-normative example of the SCIM resource type The following is a non-normative example of the SCIM resource type
representation in JSON format. representation in JSON format.
{ {
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:ResourceType"], "schemas": ["urn:ietf:params:scim:schemas:core:2.0:ResourceType"],
"id":"User", "id":"User",
"name":"User", "name":"User",
"endpoint": "/Users", "endpoint": "/Users",
"description": "Core User", "description": "User Account",
"schema": "urn:ietf:params:scim:schemas:core:2.0:User", "schema": "urn:ietf:params:scim:schemas:core:2.0:User",
"schemaExtensions": [ "schemaExtensions": [
{ {
"schema": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User", "schema": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User",
"required": true "required": true
} }
], ],
"meta": { "meta": {
"location":"https://example.com/v2/ResourceTypes/User", "location":"https://example.com/v2/ResourceTypes/User",
"resourceType": "ResourceType", "resourceType": "ResourceType",
"created": "2010-01-23T04:56:22Z", "created": "2010-01-23T04:56:22Z",
"lastModified": "2011-05-13T04:42:34Z", "lastModified": "2011-05-13T04:42:34Z",
"version": "W\/\"3694e05e9dff595\"" "version": "W\/\"3694e05e9dff595\""
} }
} }
Figure 7: Example Resource Type JSON Representation Figure 8: Example Resource Type JSON Representation
11.7. Schema Representation 8.7. Schema Representation
The following is intended as normative example of the SCIM Schema The following is intended as normative example of the SCIM Schema
representation in JSON format. Where permitted individual values and representation in JSON format. Where permitted individual values and
schema MAY change. Included but not limited to, are schemas for schema MAY change. Included but not limited to, are schemas for
User, Group, and enterprise user. User, Group, and enterprise user.
{[ {[
{ {
"id" : "urn:ietf:params:scim:schemas:core:2.0:User", "id" : "urn:ietf:params:scim:schemas:core:2.0:User",
"name" : "User", "name" : "User",
"description" : "Core User", "description" : "User Account",
"attributes" : [ "attributes" : [
{ {
"name" : "id",
"type" : "string",
"multiValued" : false,
"description" : "Unique identifier for the SCIM resource as defined by the Service Provider. Each representation of the resource MUST include a non-empty id value. This identifier MUST be unique across the Service Provider's entire set of resources. It MUST be a stable, non-reassignable identifier that does not change when the same resource is returned in subsequent requests. The value of the id attribute is always issued by the Service Provider and MUST never be specified by the Service Consumer. REQUIRED.",
"required" : true,
"caseExact" : false,
"mutability" : "readOnly",
"returned" : "always",
"uniqueness" : "server"
},
{
"name" : "externalId",
"type" : "string",
"multiValued" : false,
"description" : "An identifier for the Resource as defined by the Service Consumer.",
"required" : true,
"caseExact" : false,
"mutability" : "readWrite",
"returned" : "default",
"uniqueness" : "none"
},
{
"name" : "userName", "name" : "userName",
"type" : "string", "type" : "string",
"multiValued" : false, "multiValued" : false,
"description" : "Unique identifier for the User typically used by the user to directly authenticate to the service provider. Each User MUST include a non-empty userName value. This identifier MUST be unique across the Service Consumer's entire set of Users. REQUIRED", "description" : "Unique identifier for the User typically used by the user to directly authenticate to the service provider. Each User MUST include a non-empty userName value. This identifier MUST be unique across the Service Consumer's entire set of Users. REQUIRED",
"required" : true, "required" : true,
"caseExact" : false, "caseExact" : false,
"mutability" : "readWrite", "mutability" : "readWrite",
"returned" : "default", "returned" : "default",
"uniqueness" : "server" "uniqueness" : "server"
}, },
skipping to change at page 49, line 48 skipping to change at page 51, line 40
"resourceType" : "Schema", "resourceType" : "Schema",
"created" : "2010-01-23T04:56:22Z", "created" : "2010-01-23T04:56:22Z",
"lastModified" : "2014-02-04T00:00:00Z", "lastModified" : "2014-02-04T00:00:00Z",
"version" : "W/\"3694e05e9dff596\"", "version" : "W/\"3694e05e9dff596\"",
"location" : "https://example.com/v2/Schemas/urn:ietf:params:scim:schemas:core:2.0:User" "location" : "https://example.com/v2/Schemas/urn:ietf:params:scim:schemas:core:2.0:User"
} }
}, },
{ {
"id" : "urn:ietf:params:scim:schemas:core:2.0:Group", "id" : "urn:ietf:params:scim:schemas:core:2.0:Group",
"name" : "Group", "name" : "Group",
"description" : "Core Group", "description" : "Group",
"attributes" : [ "attributes" : [
{ {
"name" : "id",
"type" : "string",
"multiValued" : false,
"description" : "Unique identifier for the SCIM resource as defined by the Service Provider. Each representation of the resource MUST include a non-empty id value. This identifier MUST be unique across the Service Provider's entire set of resources. It MUST be a stable, non-reassignable identifier that does not change when the same resource is returned in subsequent requests. The value of the id attribute is always issued by the Service Provider and MUST never be specified by the Service Consumer. REQUIRED.",
"required" : true,
"caseExact" : false,
"mutability" : "readWrite",
"returned" : "always",
"uniqueness" : "server"
},
{
"name" : "externalId",
"type" : "string",
"multiValued" : false,
"description" : "An identifier for the Resource as defined by the Service Consumer.",
"required" : true,
"caseExact" : false,
"mutability" : "readWrite",
"returned" : "default",
"uniqueness" : "none"
},
{
"name" : "displayName", "name" : "displayName",
"type" : "string", "type" : "string",
"multiValued" : false, "multiValued" : false,
"description" : "A human readable name for the Group. REQUIRED.", "description" : "A human readable name for the Group. REQUIRED.",
"required" : false, "required" : false,
"caseExact" : false, "caseExact" : false,
"mutability" : "readWrite", "mutability" : "readWrite",
"returned" : "default", "returned" : "default",
"uniqueness" : "none" "uniqueness" : "none"
}, },
{ {
"name" : "members", "name" : "members",
"type" : "complex", "type" : "complex",
"multiValued" : false, "multiValued" : false,
"description" : "A list of members of the Group.", "description" : "A list of members of the Group.",
"required" : false, "required" : false,
"caseExact" : false, "caseExact" : false,
"subAttributes" : [ "subAttributes" : [
{ {
skipping to change at page 54, line 19 skipping to change at page 55, line 37
"meta" : { "meta" : {
"resourceType" : "Schema", "resourceType" : "Schema",
"created" : "2010-01-23T04:56:22Z", "created" : "2010-01-23T04:56:22Z",
"lastModified" : "2014-02-04T00:00:00Z", "lastModified" : "2014-02-04T00:00:00Z",
"version" : "W/\"3694e05e9dff596\"", "version" : "W/\"3694e05e9dff596\"",
"location" : "https://example.com/v2/Schemas/urn:ietf:params:scim:schemas:extension:enterprise:2.0:User" "location" : "https://example.com/v2/Schemas/urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"
} }
} }
]} ]}
Figure 8: Eample Schema JSON Representation Figure 9: Eample Schema JSON Representation
12. Security Considerations 9. Security Considerations
The SCIM Core schema contains personally identifiable information as The SCIM Core schema defines attributes that MAY contain personally
well as other sensitive data. Aside from prohibiting password values identifiable information as well as other sensitive data. Aside from
in a SCIM response this specification does not provide any means or prohibiting password values in a SCIM response this specification
guarantee of confidentiality. does not provide any means or guarantee of confidentiality.
13. IANA Considerations In particular, attributes such as "id" and "externalId" are of
particular concern as personally identifiable information that
uniquely map to Users (because they are URIs). Where possible, it is
suggested that service providers take the following remediations:
13.1. New Registration of SCIM URN Sub-namespace o Assign and bind identifiers to specific tenants and/or clients.
When mulitple tenants are able to reference the same resource,
they should do so via separate identifiers (id or externalId).
This ensures that separate domains linked to the same information
may not perform identifier correlation.
o In the case of "externalId", if multiple values are supported, use
access control to restrict access to the client domain that
assigned the "externalId" value.
o Ensure that access to data is appropriately restricted to
authorized parties with a need-to-know.
o When persisted, the appropriate protection mechanisms are in place
to restrict access by unauthorized parties including
administrators or parties with access to backup data.
It is important to note that these considerations are intentionally
general in nature. Considerations relative to the access protocol
are out of scope of the core-schema document and are addressed in
other SCIM specifications.
10. IANA Considerations
10.1. New Registration of SCIM URN Sub-namespace
IANA has created a registry for new IETF URN sub-namespaces, IANA has created a registry for new IETF URN sub-namespaces,
"urn:ietf:params:scim:", per [RFC3553]. The registration request is "urn:ietf:params:scim:", per [RFC3553]. The registration request is
as follows: as follows:
Per [RFC3553], IANA has registered a new URN sub-namespace, Per [RFC3553], IANA has registered a new URN sub-namespace,
"urn:ietf:params:scim". "urn:ietf:params:scim".
o Registry name: scim o Registry name: scim
o Specification: [this document] o Specification: [this document]
o Repository: [see Section 13.2] o Repository: [see Section 10.2]
o Index value: values [see Section 13.2] o Index value: values [see Section 10.2]
13.2. URN Sub-Namespace for SCIM 10.2. URN Sub-Namespace for SCIM
SCIM schemas and SCIM messages utilize URIs to identify the schema in SCIM schemas and SCIM messages utilize URIs to identify the schema in
use or other relevant context. This section creates and registers an use or other relevant context. This section creates and registers an
IETF URN Sub-namespace for use in the SCIM specifications and future IETF URN Sub-namespace for use in the SCIM specifications and future
extensions. extensions.
13.2.1. Specification Template 10.2.1. Specification Template
Namespace ID: Namespace ID:
The Namespace ID "scim" is requested. The Namespace ID "scim" is requested.
Registration Information: Registration Information:
Version: 1 Version: 1
Date: [[insert final submission date]] Date: [[insert final submission date]]
skipping to change at page 55, line 33 skipping to change at page 57, line 31
Designated contact Designated contact
A designated expert will monitor the SCIM public mailing list, A designated expert will monitor the SCIM public mailing list,
"scim@ietf.org". "scim@ietf.org".
Declaration of Syntactic Structure: Declaration of Syntactic Structure:
The Namespace Specific String (NSS) of all URNs that use the The Namespace Specific String (NSS) of all URNs that use the
"scim" NID shall have the following structure: "scim" NID shall have the following structure:
urn:ietf:params:scim:{type}:{name}{:sName}:{vers}{:class}{:resType} urn:ietf:params:scim:{type}:{name}{:other}
The keywords have the following meaning: The keywords have the following meaning:
type type
The entity type which is either "schemas" or "api". The entity type which is either "schemas" or "api".
name name
A required US-ASCII string that conforms to the URN syntax A required US-ASCII string that conforms to the URN syntax
requirements (see [RFC2141] ) and defines a major namespace of requirements (see [RFC2141] ) and defines a major namespace of
object used within SCIM (e.g. "core", "extension" ). The name a schema used within SCIM (e.g. "core" in the case of SCIM Core
"extension" MAY be used when the registered schema it refers to Schema). The value MAY also be an industry name or
is intended to be used as an extension to another schema. organization name.
An optional US-ASCII string that conforms to the URN syntax
requirements (see [RFC2141] ) and defines a sub-class of object
used within SCIM (e.g. "enterprise").
vers
The first SCIM protocol version number where the URN is valid
(e.g. "2.0" ).
class
An optional US-ASCII string that conforms to the URN syntax
requirements (see [RFC2141] ) and defines a major class of
object used within SCIM.
resType other
An optional US-ASCII string that conforms to the URN syntax Any US-ASCII string that conforms to the URN syntax
requirements (see [RFC2141] ) and typically is used when requirements (see [RFC2141] ) and defines the sub-namespace
referring to a resource type within SCIM (e.g. User). (which MAY be further broken down in namespaces delimited by
colons) as needed to uniquely identify a schema.
Relevant Ancillary Documentation: Relevant Ancillary Documentation:
None None
Identifier Uniqueness Considerations: Identifier Uniqueness Considerations:
The designated contact shall be responsible for reviewing and The designated contact shall be responsible for reviewing and
enforcing uniqueness. enforcing uniqueness.
skipping to change at page 56, line 48 skipping to change at page 58, line 32
significant changes are made. Example, significant changes are made. Example,
"urn:ietf:params:scim:schemas:core:1.0 (externally defined, not "urn:ietf:params:scim:schemas:core:1.0 (externally defined, not
previously registered)" and previously registered)" and
"urn:ietf:params:scim:schemas:core:2.0". "urn:ietf:params:scim:schemas:core:2.0".
Process of Identifier Assignment: Process of Identifier Assignment:
Identifiers with namespace type "schema" (e.g. Identifiers with namespace type "schema" (e.g.
"urn:ietf:params:scim:schemas" ) are assigned after the review of "urn:ietf:params:scim:schemas" ) are assigned after the review of
the assigned contact via the SCIM public mailing list, the assigned contact via the SCIM public mailing list,
"scim@ietf.org" as documented in Section 13.3. "scim@ietf.org" as documented in Section 10.3.
Namespaces with type "api" (e.g. "urn:ietf:params:scim:api" ) are Namespaces with type "api" (e.g. "urn:ietf:params:scim:api" ) are
reserved for IETF approved SCIM specifications. Namespaces with reserved for IETF approved SCIM specifications. Namespaces with
type "param" are reserved for future use. type "param" are reserved for future use.
Process of Identifier Resolution: Process of Identifier Resolution:
The namespace is not currently listed with a Resolution Discovery The namespace is not currently listed with a Resolution Discovery
System (RDS), but nothing about the namespace prohibits the future System (RDS), but nothing about the namespace prohibits the future
definition of appropriate resolution methods or listing with an definition of appropriate resolution methods or listing with an
skipping to change at page 57, line 29 skipping to change at page 59, line 13
No special considerations. No special considerations.
Validation Mechanism: Validation Mechanism:
None specified. None specified.
Scope: Scope:
Global. Global.
13.2.2. Pre-Registered SCIM Schema Identifiers 10.2.2. Pre-Registered SCIM Schema Identifiers
The following SCIM Identifiers are defined: The following SCIM Identifiers are defined:
urn:ietf:params:scim:schemas:core:2.0 urn:ietf:params:scim:schemas:core:2.0
SCIM Core Schema as specified in Section 4 and Section 13.4. SCIM Core Schema as specified in Section 4 and Section 10.4.
urn:ietf:params:scim:schemas:extension:enterprise:2.0 urn:ietf:params:scim:schemas:extension:enterprise:2.0
Enterprise schema extensions as defined in Section 6 and Enterprise schema extensions as defined in Section 4.3 and
Section 13.4. Section 10.4.
13.3. Registering SCIM Schemas 10.3. Registering SCIM Schemas
This section defines the process for registering new SCIM schemas This section defines the process for registering new SCIM schemas
with IANA. A schema URI is used as a value in the schemas attribute with IANA. A schema URI is used as a value in the schemas attribute
( Section 4.2 ) for the purpose of distinguishing extensions used in (Section 3) for the purpose of distinguishing extensions used in a
a SCIM resource. SCIM resource.
13.3.1. Registration Procedure 10.3.1. Registration Procedure
The IETF has created a mailing list, scim@ietf.org, which can be used The IETF has created a mailing list, scim@ietf.org, which can be used
for public discussion of SCIM schema proposals prior to registration. for public discussion of SCIM schema proposals prior to registration.
Use of the mailing list is strongly encouraged. The IESG has Use of the mailing list is strongly encouraged. The IESG has
appointed a designated expert who will monitor the scim@ietf.org appointed a designated expert who will monitor the scim@ietf.org
mailing list and review registrations. mailing list and review registrations.
Registration of new schemas MUST be reviewed by the designated expert Registration of new schemas MUST be reviewed by the designated expert
and published in an RFC. A Standards Track RFC is REQUIRED for the and published in an RFC. A Standards Track RFC is REQUIRED for the
registration of new value data types that modify existing properties. registration of new value data types that modify existing properties.
skipping to change at page 58, line 41 skipping to change at page 60, line 20
Once the registration procedure concludes successfully, IANA creates Once the registration procedure concludes successfully, IANA creates
or modifies the corresponding record in the SCIM schema registry. or modifies the corresponding record in the SCIM schema registry.
The completed registration template is discarded. The completed registration template is discarded.
An RFC specifying new schema URI MUST include the completed An RFC specifying new schema URI MUST include the completed
registration templates, which MAY be expanded with additional registration templates, which MAY be expanded with additional
information. These completed templates are intended to go in the information. These completed templates are intended to go in the
body of the document, not in the IANA Considerations section. The body of the document, not in the IANA Considerations section. The
RFC SHOULD include any attributes defined. RFC SHOULD include any attributes defined.
13.3.2. Schema Registration Template 10.3.2. Schema Registration Template
A SCIM schema URI is defined by completing the following template: A SCIM schema URI is defined by completing the following template:
Schema URI: Schema URI: A unique URI for the SCIM schema extension. Schema URI: Schema URI: A unique URI for the SCIM schema extension.
Schema Name: A descriptive name of the schema extension (e.g. Schema Name: A descriptive name of the schema extension (e.g.
Generic Device) Generic Device)
Intended or Associated Resource Type: A value defining the resource Intended or Associated Resource Type: A value defining the resource
type (e.g. "Device"). type (e.g. "Device").
Purpose: A description of the purpose of the extension and/or its Purpose: A description of the purpose of the extension and/or its
intended use. intended use.
Single-value Attributes: A list and description of single-valued Single-value Attributes: A list and description of single-valued
attributes defined including complex attributes. attributes defined including complex attributes.
Multi-valued Attributes: A list and description of multi-valued Multi-valued Attributes: A list and description of multi-valued
attributes defined including complex attributes. attributes defined including complex attributes.
13.4. Initial SCIM Schema Registry 10.4. Initial SCIM Schema Registry
The IANA has created and will maintain the following registries for The IANA has created and will maintain the following registries for
SCIM schema URIs with pointers to appropriate reference documents. SCIM schema URIs with pointers to appropriate reference documents.
Note: the Schema URI broken into two lines for readability.
+----------------------------------------------+---------+----------+ +-----------------------------------+-----------------+-------------+
| Schema URI | Name | Referenc | | Schema URI | Name | Reference |
| | | e | +-----------------------------------+-----------------+-------------+
+----------------------------------------------+---------+----------+ | urn:ietf:params:scim:schemas: | User Resource | See Section |
| urn:ietf:params:scim:schemas:core:2.0:User | User Re | See | | core:2.0:User | | 4.1 |
| | source | Section | | urn:ietf:params:scim:schemas: | Enterprise User | See Section |
| | | 5 | | extension:enterprise:2.0:User | Extension | 4.3 |
| urn:ietf:params:scim:schemas:extension:enter | Enterpr | See | | urn:ietf:params:scim:schemas: | Group Resource | See Section |
| prise:2.0:User | ise | Section | | core:2.0:Group | | 4.2 |
| | User Ex | 6 | +-----------------------------------+-----------------+-------------+
| | tension | |
| urn:ietf:params:scim:schemas:core:2.0:Group | Group R | See |
| | esource | Section |
| | | 7 |
+----------------------------------------------+---------+----------+
SCIM Schema URIs for Data Resources SCIM Schema URIs for Data Resources
+--------------------------------------------+-----------+----------+ +-----------------------------------+-------------------+-----------+
| Schema URI | Name | Referenc | | Schema URI | Name | Reference |
| | | e | +-----------------------------------+-------------------+-----------+
+--------------------------------------------+-----------+----------+ | urn:ietf:params:scim:schemas: | Service Provider | See |
| urn:ietf:params:scim:schemas:core:2.0:Serv | Service | See | | core:2.0:ServiceProviderConfig | Configuration | Section 5 |
| iceProviderConfig | Provider | Section | | | Schema | |
| | Configura | 8 | | urn:ietf:params:scim:schemas: | Resource Type | See |
| | tion | | | core:2.0:ResourceType | Config | Section 6 |
| | Schema | | | urn:ietf:params:scim:schemas: | Schema | See |
| urn:ietf:params:scim:schemas:core:2.0:Reso | Resource | See | | core:2.0:Schema | Definitions | Section 7 |
| urceType | Type | Section | | | Schema | |
| | Config | 9 | +-----------------------------------+-------------------+-----------+
| urn:ietf:params:scim:schemas:core:2.0:Sche | Schema De | See |
| ma | finitions | Section |
| | Schema | 10 |
+--------------------------------------------+-----------+----------+
SCIM Server Related Schema URIs SCIM Server Related Schema URIs
14. References 11. References
14.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An [RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An
IETF URN Sub-namespace for Registered Protocol IETF URN Sub-namespace for Registered Protocol
Parameters", BCP 73, RFC 3553, June 2003. Parameters", BCP 73, RFC 3553, June 2003.
skipping to change at page 61, line 21 skipping to change at page 62, line 31
[RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, March 2014. Interchange Format", RFC 7159, March 2014.
[RFC7231] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol [RFC7231] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol
(HTTP/1.1): Semantics and Content", RFC 7231, June 2014. (HTTP/1.1): Semantics and Content", RFC 7231, June 2014.
[XML-Schema] [XML-Schema]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Second Edition", October 2004. Second Edition", October 2004.
14.2. Informative References 11.2. Informative References
[ISO3166] "ISO 3166:1988 (E/F) - Codes for the representation of [ISO3166] "ISO 3166:1988 (E/F) - Codes for the representation of
names of countries - The International Organization for names of countries - The International Organization for
Standardization, 3rd edition", 08 1988. Standardization, 3rd edition", 08 1988.
[ISO639-2] [ISO639-2]
ISO 639.2 Registration Authority, "ISO639-2: Codes for the ISO 639.2 Registration Authority, "ISO639-2: Codes for the
Representation of Names of Languages", July 2013. Representation of Names of Languages", July 2013.
[Olson-TZ] [Olson-TZ]
skipping to change at page 64, line 31 skipping to change at page 65, line 41
Removed duplicate text from Schema Schema section Removed duplicate text from Schema Schema section
Removed "operation" attribute from Multi-valued Attribute sub- Removed "operation" attribute from Multi-valued Attribute sub-
attribute definitions. This was used in the old PATCH command and attribute definitions. This was used in the old PATCH command and
is no longer valid. is no longer valid.
Revised some layout to make indentation and definition of Revised some layout to make indentation and definition of
attributes more clear (added vspace elements) attributes more clear (added vspace elements)
Authors' Addresses Draft 10 - PH - Editorial revisions
Kelly Grizzle Simplified namespace definition for urn:ietf:params:scim
SailPoint
Email: kelly.grizzle@sailpoint.com Clarified "schemas" attribute as representing the JSON body schema
in an HTTP Req/Resp
Reduced use of confusing term "core" in "Core User" and "Core
Group"
Added clarifications and security considerations for externalId
Re-worded descriptions SCIM schema extension model (sec 3) and
core schema (sec 4) for improved clarity
Authors' Addresses
Phil Hunt (editor) Phil Hunt (editor)
Oracle Corporation Oracle Corporation
Email: phil.hunt@yahoo.com Email: phil.hunt@yahoo.com
Kelly Grizzle
SailPoint
Email: kelly.grizzle@sailpoint.com
Erik Wahlstroem Erik Wahlstroem
Nexus Technology Nexus Technology
Email: erik.wahlstrom@nexusgroup.com Email: erik.wahlstrom@nexusgroup.com
Chuck Mortimore Chuck Mortimore
Salesforce.com Salesforce.com
Email: cmortimore@salesforce.com Email: cmortimore@salesforce.com
 End of changes. 95 change blocks. 
312 lines changed or deleted 384 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/