draft-ietf-scim-use-cases-08.txt   rfc7642.txt 
SCIM WG K. LI, Ed. Internet Engineering Task Force (IETF) K. LI, Ed.
Internet-Draft Alibaba Group Request for Comments: 7642 Alibaba Group
Intended status: Informational P. Hunt Category: Informational P. Hunt
Expires: November 8, 2015 Oracle ISSN: 2070-1721 Oracle
B. Khasnabish B. Khasnabish
ZTE (TX) Inc. ZTE (TX) Inc.
A. Nadalin A. Nadalin
Microsoft Microsoft
Z. Zeltsan Z. Zeltsan
Individual Individual
May 7, 2015 September 2015
SCIM Definitions, Overview, Concepts and Requirements System for Cross-domain Identity Management:
draft-ietf-scim-use-cases-08 Definitions, Overview, Concepts, and Requirements
Abstract Abstract
This document provides definitions and an overview of the System for This document provides definitions and an overview of the System for
Cross-domain Identity Management (SCIM). It lays out the system's Cross-domain Identity Management (SCIM). It lays out the system's
concepts, models and flows, and includes user scenarios, use cases, concepts, models, and flows, and it includes user scenarios, use
and requirements. cases, and requirements.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is not an Internet Standards Track specification; it is
Task Force (IETF). Note that other groups may also distribute published for informational purposes.
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on November 8, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7642.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. SCIM User Scenarios . . . . . . . . . . . . . . . . . . . . . 4 2. SCIM User Scenarios . . . . . . . . . . . . . . . . . . . . . 5
2.1. Background & Context . . . . . . . . . . . . . . . . . . . 4 2.1. Background and Context . . . . . . . . . . . . . . . . . 5
2.2. Model Concepts . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Model Concepts . . . . . . . . . . . . . . . . . . . . . 5
2.2.1. Triggers . . . . . . . . . . . . . . . . . . . . . . . 4 2.2.1. Triggers . . . . . . . . . . . . . . . . . . . . . . 5
2.2.2. Actors . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2.2. Actors . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.3. Modes & Flows . . . . . . . . . . . . . . . . . . . . 6 2.2.3. Modes and Flows . . . . . . . . . . . . . . . . . . . 7
2.2.4. Bulk & Batch Operational Semantics . . . . . . . . . . 7 2.2.4. Bulk and Batch Operational Semantics . . . . . . . . 8
2.3. Cloud Service Provider to Cloud Service Provider Flows 2.3. Flows from Cloud Service Provider to Cloud Service
(CSP->CSP) . . . . . . . . . . . . . . . . . . . . . . . . 7 Provider (CSP->CSP) . . . . . . . . . . . . . . . . . . . 8
2.3.1. CSP->CSP - Create Identity (Push) . . . . . . . . . . 7 2.3.1. CSP->CSP: Create Identity (Push) . . . . . . . . . . 8
2.3.2. CSP->CSP - Update Identity (Push) . . . . . . . . . . 7 2.3.2. CSP->CSP: Update Identity (Push) . . . . . . . . . . 9
2.3.3. CSP->CSP - Delete Identity (Push) . . . . . . . . . . 8 2.3.3. CSP->CSP: Delete Identity (Push) . . . . . . . . . . 9
2.3.4. CSP->CSP - SSO Trigger (Push) . . . . . . . . . . . . 8 2.3.4. CSP->CSP: SSO Trigger (Push) . . . . . . . . . . . . 9
2.3.5. CSP->CSP - SSO Trigger (Pull) . . . . . . . . . . . . 8 2.3.5. CSP->CSP: SSO Trigger (Pull) . . . . . . . . . . . . 10
2.3.6. CSP->CSP - Password Reset (Push) . . . . . . . . . . . 9 2.3.6. CSP->CSP: Password Reset (Push) . . . . . . . . . . . 10
2.4. Enterprise Cloud Subscriber to Cloud Service Provider 2.4. Flows from Enterprise Cloud Subscriber to Cloud Service
Flows(ECS->CSP) . . . . . . . . . . . . . . . . . . . . . 9 Provider (ECS->CSP) . . . . . . . . . . . . . . . . . 10
2.4.1. ECS->CSP - Create Identity (Push) . . . . . . . . . . 9 2.4.1. ECS->CSP: Create Identity (Push) . . . . . . . . . . 10
2.4.2. ECS ->CSP - Update Identity (Push) . . . . . . . . . . 9 2.4.2. ECS->CSP: Update Identity (Push) . . . . . . . . . . 11
2.4.3. ECS ->CSP - Delete Identity (Push) . . . . . . . . . . 10 2.4.3. ECS->CSP: Delete Identity (Push) . . . . . . . . . . 11
2.4.4. ECS ->CSP - SSO Pull . . . . . . . . . . . . . . . . . 10 2.4.4. ECS->CSP: SSO Trigger (Pull) . . . . . . . . . . . . 11
3. SCIM Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 10 3. SCIM Use Cases . . . . . . . . . . . . . . . . . . . . . . . 11
3.1. Migration of the identities . . . . . . . . . . . . . . . 10 3.1. Migration of the Identities . . . . . . . . . . . . . . . 11
3.2. Single Sign-On (SSO) Service . . . . . . . . . . . . . . . 11 3.2. Single Sign-On (SSO) Service . . . . . . . . . . . . . . 12
3.3. Provisioning of the user accounts for a Community of 3.3. Provisioning of the User Accounts for a Community of
Interest (CoI) . . . . . . . . . . . . . . . . . . . . . . 13 Interest (COI) . . . . . . . . . . . . . . . . . . . . . 14
3.4. Transfer of attributes to a relying party web site . . . . 14 3.4. Transfer of Attributes to a Relying Party's Website . . . 15
3.5. Change notification . . . . . . . . . . . . . . . . . . . 15 3.5. Change Notification . . . . . . . . . . . . . . . . . . . 16
4. Security considerations . . . . . . . . . . . . . . . . . . . 16 4. Security Considerations . . . . . . . . . . . . . . . . . . . 17
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 17 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 5.1. Normative References . . . . . . . . . . . . . . . . . . 18
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.2. Informative References . . . . . . . . . . . . . . . . . 18
7.1. Normative References . . . . . . . . . . . . . . . . . . . 17 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2. Informative References . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
This document provides the SCIM definitions, overview, concepts, This document provides the SCIM definitions, overview, concepts,
flows, scenarios and use cases. It also provides a list of the flows, scenarios, and use cases. It also provides a list of the
requirements derived from the use cases. requirements derived from the use cases.
The document's objective is to help with understanding of the design The document's objective is to help with understanding of the design
and applicability of SCIM schema [I-D.ietf-scim-core-schema] and SCIM and applicability of the SCIM schema [RFC7643] and SCIM protocol
protocol [I-D.ietf-scim-api]. [RFC7644].
Unlike the practice of some protocols like ABFAB and SAML2 WebSSO, Unlike the practice of some protocols like Application Bridging for
SCIM provides provisioning and de-provisioning of resources in a Federated Access Beyond web (ABFAB) and SAML2 WebSSO, SCIM provides
separate context from authentication (aka just-in-time provisioning). provisioning and de-provisioning of resources in a separate context
from authentication (aka just-in-time provisioning).
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119] when they document are to be interpreted as described in [RFC2119] when they
appear in ALL CAPS. These words may also appear in this document in appear in ALL CAPS. These words may also appear in this document in
lower case as plain English words, absent their normative meanings. lowercase as plain English words, absent their normative meanings.
Here is a list of acronyms and abbreviations used in this document: Here is a list of acronyms and abbreviations used in this document:
o COI: Community Of Interest o COI: Community of Interest
o CRM: Customer Relationship Management o CRM: Customer Relationship Management
o CRUD: Create Read Update Delete o CRUD: Create, Read, Update, Delete
o CSP: Cloud Service Provider o CSP: Cloud Service Provider
o CSU: Cloud Service User o CSU: Cloud Service User
o ECS: Enterprise Cloud Subscriber o ECS: Enterprise Cloud Subscriber
o IaaS: Infrastructure as a Service o IaaS: Infrastructure as a Service
o JIT: Just In Time o JIT: Just In Time
skipping to change at page 3, line 50 skipping to change at page 5, line 4
o IaaS: Infrastructure as a Service o IaaS: Infrastructure as a Service
o JIT: Just In Time o JIT: Just In Time
o PaaS: Platform as a Service o PaaS: Platform as a Service
o SaaS: Software as a Service o SaaS: Software as a Service
o SAML: Security Assertion Markup Language o SAML: Security Assertion Markup Language
o SCIM: System for Cross-domain Identity Management o SCIM: System for Cross-domain Identity Management
o SSO: Single-Sign On
o SSO: Single Sign-On
2. SCIM User Scenarios 2. SCIM User Scenarios
2.1. Background & Context 2.1. Background and Context
The System for Cross-domain Identity Management (SCIM) specification The System for Cross-domain Identity Management (SCIM) specification
is designed to manage user identity in cloud based applications and is designed to manage user identity in cloud-based applications and
services in a standardized way to enable interoperability, security services in a standardized way to enable interoperability, security,
and scalability. The specification suite seeks to build upon and scalability. The specification suite seeks to build upon
experience with existing schemas and deployments, placing specific experience with existing schemas and deployments, placing specific
emphasis on simplicity of development and integration, while applying emphasis on simplicity of development and integration, while applying
existing authentication, authorization, and privacy models. The existing authentication, authorization, and privacy models. The
intent of SCIM specification is to reduce the cost and complexity of intent of the SCIM specification is to reduce the cost and complexity
user management operations by providing a common user schema and of user management operations by providing a common user schema and
extension model, as well as binding documents to provide patterns for extension model, as well as binding documents to provide patterns for
exchanging this schema using standard protocols. In essence, make it exchanging this schema using standard protocols. In essence, make it
fast, cheap, and easy to move users in to, out of, and around the fast, cheap, and easy to move users in to, out of, and around the
cloud. cloud.
The SCIM scenarios are overview user stories designed to help clarify The SCIM scenarios are overviews of user stories designed to help
the intended scope of the SCIM effort. clarify the intended scope of the SCIM effort.
2.2. Model Concepts 2.2. Model Concepts
2.2.1. Triggers 2.2.1. Triggers
Quite simply, triggers are actions or activities that start SCIM Quite simply, triggers are actions or activities that start SCIM
flows. Triggers may not be relevant at the protocol or the schema, flows. Triggers may not be relevant at the protocol level or the
they really serve to help identify the type or activity that resulted schema level; they really serve to help identify the type or activity
in a SCIM protocol exchange. Triggers make use of the traditional that resulted in a SCIM protocol exchange. Triggers make use of the
provisioning CRUD (Create Read Update & Delete) operations but add traditional provisioning CRUD (Create, Read, Update, Delete)
additional use case contexts like "SSO" (Single-Sign On) as it is operations but add additional use-case contexts like SSO (Single-Sign
designed to capture a class of use case that makes sense to the actor On) as it is designed to capture a class of use case that makes sense
requesting it rather than to describe a protocol operation. to the actor requesting it rather than to describe a protocol
operation.
o Create SCIM Identity Resource - Service On-boarding Trigger: A o Create SCIM Identity Resource - Service On-boarding Trigger: A
"create SCIM identity resource" trigger is a service on-boarding "create SCIM identity resource" trigger is a service on-boarding
activity in which a business action such as a new hire or new activity in which a business action such as a new hire or new
service subscription is initiated by one of the SCIM Actors. In service subscription is initiated by one of the SCIM Actors. In
the protocol itself, service on-boarding may well be implemented the protocol itself, service on-boarding may well be implemented
via the same resource PUT method as a service change. This is via the same resource PUT method as a service change. This is
particular to the implementation, and not to the use cases that particular to the implementation, and not to the use cases that
drive that implementation. drive that implementation.
o Update SCIM Identity Resource - Service Change Trigger: An "update o Update SCIM Identity Resource - Service Change Trigger: An "update
SCIM identity resource" trigger is a service change activity as a SCIM identity resource" trigger is a service change activity as a
result of an identity moving or changing its service level. An result of an identity moving or changing its service level. An
"update SCIM identity" trigger might be the result of a change in "update SCIM identity" trigger might be the result of a change in
a service subscription level or a change to key identity data used a service subscription level or a change to key identity data used
to denote a service subscription level. Password changes are to denote a service subscription level. Password changes are
specifically called out from other more general identity attribute specifically called out from other more general identity attribute
changes as they are considered to have specific use case changes as they are considered to have specific use-case
differences. differences.
o Delete SCIM Identity Resource - Service Termination Trigger: A o Delete SCIM Identity Resource - Service Termination Trigger: A
"delete SCIM identity resource" trigger represents a specific and "delete SCIM identity resource" trigger represents a specific and
deliberate action to remove an identity from a given SCIM service deliberate action to remove an identity from a given SCIM service
point. At this stage it is unclear if the SCIM protocol needs to point. At this stage, it is unclear if the SCIM protocol needs to
identify separate protocol exchange for a service suspension identify a separate protocol exchange for service suspension
actions. This may be relevant as target services usually actions. This may be relevant as target services usually
differentiate between these result and may require separate differentiate between these results and thus may require separate
resource representations as a result. resource representations.
o Single-Sign On (SSO) Trigger - Service Access Request: A "Single- o Single Sign-On (SSO) Trigger - Service Access Request: A "Single
Sign On" trigger is a special class of activity in which a Create Sign-On" trigger is a special class of activity in which a Create
or Update trigger is initiated during an SSO operational flow. or Update trigger is initiated during an SSO operational flow.
The implication here is that as the result of a service access The implication here is that, as the result of a service access
request by the end user (SSO), defined SCIM protocol exchanges can request by the end user (SSO), defined SCIM protocol exchanges can
be used to initiate SCIM resource CRUD somewhere in the service be used to initiate SCIM resource CRUD operations somewhere in the
cloud. service cloud.
2.2.2. Actors 2.2.2. Actors
Actors are the operating parties that take part in both sides of a Actors are the operating parties that take part in both sides of a
SCIM protocol exchange, and help identify the source of a given SCIM protocol exchange and help identify the source of a given
Trigger. So far, we have identified the following SCIM Actors: Trigger. So far, we have identified the following SCIM Actors:
o Cloud Service Provider (CSP): A CSP is the entity operating a o Cloud Service Provider (CSP): A CSP is the entity operating a
given cloud service. In a SaaS scenario this is simply the given cloud service. In a SaaS scenario, this is simply the
application provider. In an IaaS or PaaS scenario, the CSP may be application provider. In an IaaS or PaaS scenario, the CSP may be
the underlying IaaS/PaaS infrastructure provider or the owner of the underlying IaaS/PaaS infrastructure provider or the owner of
the application running on that platform. In all cases, the CSP the application running on that platform. In all cases, the CSP
is the thing that holds the identity information being operated is the thing that holds the identity information being operated
upon. Put another way, the CSP really is the service that the upon. Put another way, the CSP really is the service that the end
end-end user interacts with. user interacts with.
o Enterprise Cloud Subscriber (ECS): An ECS represents a middle-tier o Enterprise Cloud Subscriber (ECS): An ECS represents a middle tier
of aggregation for related identity records. In one of our sample of aggregation for related identity records. In one of our sample
enterprise SaaS scenarios, the ECS is "Example.com" that enterprise SaaS scenarios, the ECS is "Example.com" that
subscribes to a cloud based CRM service service "SaaS-CRM.Inc" subscribes to a cloud-based CRM service "SaaS-CRM Inc." (the CSP)
(the CSP) for all of its sales staff. The actual Cloud Service for all of its sales staff. The actual Cloud Service Users (CSUs)
Users (CSUs) are the FooBar.Inc. sales staff. The ECS actor is are the FooBar Inc. sales staff. The ECS Actor is identified to
identified to help capture use cases in which a single entity is help capture use cases in which a single entity is given
given administrative responsibility for other identity accounts. administrative responsibility for other identity accounts. SCIM
may not address the configuration and setup of an ECS within the
SCIM may not address the configuration and setup of an ECS within CSP, but it does address use cases in which SCIM identity
the CSP, but it does address use cases in which SCIM identity resources are grouped together and administered as part of some
resources are grouped together and administers as part of some
broader agreement or operational exchange. broader agreement or operational exchange.
o Cloud Service User (CSU): A CSU represents the real cloud service o Cloud Service User (CSU): A CSU represents the real cloud service
end user - the "person logging into and using the cloud service". end user -- i.e., the person logging into and using the cloud
As described above, and ECS will typically own or manage multiple service. As described above, and ECS will typically own or manage
CSU identities where as the CSU represents the FooBar.Inc. multiple CSU identities, whereas the CSU represents the FooBar
employee using the cloud service to manage their CRM process. Inc. employee using the cloud service to manage their CRM process.
+---------------------+ +---------------------+
| Cloud Service | | Cloud Service |
| Provider (CSP) | | Provider (CSP) |
+---------------------+ +---------------------+
| |
+--------------------------------+ +--------------------------------+
| | | |
v v v v
+----------------+ +----------------+ +----------------+ +----------------+
|Enterprise Cloud| |Enterprise Cloud| |Enterprise Cloud| |Enterprise Cloud|
|Subscriber (ECS)| |Subscriber (ECS | |Subscriber (ECS)| |Subscriber (ECS)|
+----------------+ +----------------+ +----------------+ +----------------+
| | | |
+----------------+ +----------------+ +----------------+ +----------------+
| | | | | | | |
v v v v v v v v
+-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+
|Cloud Service| |Cloud Service| |Cloud Service| |Cloud Service| |Cloud Service| |Cloud Service| |Cloud Service| |Cloud Service|
| User (CSU) | | User (CSU) | | User (CSU) | | User (CSU) | | User (CSU) | | User (CSU) | | User (CSU) | | User (CSU) |
+-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+ +-------------+
Figure 1: SCIM Actors Figure 1: SCIM Actors
2.2.3. Modes & Flows 2.2.3. Modes and Flows
Modes identify the functional intent of a data-flow initiated in a Modes identify the functional intent of a data flow initiated in a
SCIM scenario. The modes identified so far are 'push' and 'pull' SCIM scenario. The modes identified so far are 'Push' and 'Pull'
referring to the fact of pushing data to, or pulling data from an referring to pushing data to and pulling data from an authoritative
authoritative identity data store. identity data store.
In the SCIM scenarios, Modes are often used in the context of a flow In the SCIM scenarios, modes are often used in the context of a flow
between two Actors. For example, one might refer to a Cloud-to-Cloud between two Actors. For example, one might refer to a Cloud-to-Cloud
Pull exchange. Here one Cloud Service Provider (CSP) is pulling Pull exchange. Here one Cloud Service Provider (CSP) is pulling
identity information from another CSP. Commonly referenced flows identity information from another CSP. Commonly referenced flows
are: are:
o Cloud Service Provider to Cloud Service Provider (CSP->CSP) o Cloud Service Provider to Cloud Service Provider (CSP->CSP)
o Enterprise Cloud Subscriber to Cloud Service Provider (ECS-CSP) o Enterprise Cloud Subscriber to Cloud Service Provider (ECS->CSP)
Modes & flows simply help us understand what is taking place; they Modes and flows simply help us understand what is taking place; they
are likely to be technically meaningless at the protocol level, but are likely to be technically meaningless at the protocol level, but
again they help the reader follow the SCIM scenarios and apply them they help the reader follow the SCIM scenarios and apply them to
to real world use cases. real-world use cases.
2.2.4. Bulk & Batch Operational Semantics 2.2.4. Bulk and Batch Operational Semantics
It is assumed that each of the triggers action outlined in this It is assumed that each of the trigger actions outlined in this
document may be part of the larger bulk or batch operation. document may be part of the larger bulk or batch operation.
Individual SCIM actions should be able to be collected together to Individual SCIM actions should be able to be collected together to
create single protocol exchanges. create single protocol exchanges.
The initial focus of SCIM scenarios is on identifying base flows and The initial focus of SCIM scenarios is on identifying base flows and
single operations. The specific complexity of full bulk and batch single operations. The specific complexity of full bulk and batch
operations is left to a later version of the scenarios or to the main operations is left to a later version of the scenarios or to the main
specification. specification.
2.3. Cloud Service Provider to Cloud Service Provider Flows (CSP->CSP) 2.3. Flows from Cloud Service Provider to Cloud Service Provider
(CSP->CSP)
These scenarios represent flows between two Cloud Service Providers These scenarios represent flows between two Cloud Service Providers
(CSPs). It is assumed that each CSP maintains an Identity Data Store (CSPs). It is assumed that each CSP maintains an Identity Data Store
for its Cloud Service Users (CSUs). These scenarios address various for its Cloud Service Users (CSUs). These scenarios address various
joiner, mover, leaver and JIT triggers, resulting in push and pull joiner, mover, leaver, and JIT triggers, resulting in push and pull
data exchanges between the CSPs. data exchanges between the CSPs.
2.3.1. CSP->CSP - Create Identity (Push) 2.3.1. CSP->CSP: Create Identity (Push)
In this scenario two CSPs (CSP-1 & CSP-2) have a shared service In this scenario, two CSPs (CSP-1 and CSP-2) have a shared service
agreement in place that requires the exchange of Cloud Service User agreement in place that requires the exchange of Cloud Service User
(CSU) accounts. CSP-1 receives a Create Identity trigger action from (CSU) accounts. CSP-1 receives a Create Identity trigger action from
its Enterprise Cloud Subscriber (ECS-1). CSP-1 creates a local user its Enterprise Cloud Subscriber (ECS-1). CSP-1 creates a local user
account for the new CSU. CSP-1 then pushes the new CSU joiner push account for the new CSU. CSP-1 then pushes the new CSU joiner push
request down-stream to CSU-2 and gets confirmation that the account request downstream to CSU-2 and gets confirmation that the account
was successfully created. After receiving the confirmation from was successfully created. After receiving the confirmation from CSP-
CSP-2, CSP-1 sends an acknowledgement to the requesting ECS. 2, CSP-1 sends an acknowledgment to the requesting ECS.
2.3.2. CSP->CSP - Update Identity (Push) 2.3.2. CSP->CSP: Update Identity (Push)
In this scenario two CSPs (CSP-1 & CSP-2) have a shared service In this scenario, two CSPs (CSP-1 and CSP-2) have a shared service
agreement in place that requires the exchange of Cloud Service User agreement in place that requires the exchange of Cloud Service User
(CSU) accounts. The Enterprise Cloud Subscriber (ECS-1) has already (CSU) accounts. The Enterprise Cloud Subscriber (ECS-1) has already
created an account with CSP-1 and supplied a critical attribute created an account with CSP-1 and supplied a critical attribute
"department" that is used by CSP-1 to drive service options. CSP-1 "department" that is used by CSP-1 to drive service options. CSP-1
then receives an Update Identity trigger action from its Enterprise then receives an Update Identity trigger action from its Enterprise
Cloud Subscriber (ECS). CSP-1 updates its local directory account Cloud Subscriber (ECS). CSP-1 updates its local directory account
with the new department value. CSP-1 then initiates a separate SCIM with the new department value. CSP-1 then initiates a separate SCIM
protocol exchange to push the mover change request down-stream to protocol exchange to push the mover change request downstream to CSP-
CSP-2. After receiving the confirmation from CSP-2, CSP-1 sends an 2. After receiving the confirmation from CSP-2, CSP-1 sends an
acknowledgment to ECS-1. acknowledgment to ECS-1.
2.3.3. CSP->CSP - Delete Identity (Push) 2.3.3. CSP->CSP: Delete Identity (Push)
In this scenario two CSPs (CSP-1 & CSP-2) have a shared service In this scenario, two CSPs (CSP-1 and CSP-2) have a shared service
agreement in place that requires the exchange of Cloud Service User agreement in place that requires the exchange of Cloud Service User
(CSU) accounts. CSP-1 receives a Delete Identity trigger action from (CSU) accounts. CSP-1 receives a Delete Identity trigger action from
its Enterprise Cloud Subscriber (ECS-1). CSP-1 suspends the local its Enterprise Cloud Subscriber (ECS-1). CSP-1 suspends the local
directory account for the specified CSU account. CSP-1 then pushes a directory account for the specified CSU account. CSP-1 then pushes a
termination request for the specified CSU account down-stream to termination request for the specified CSU account downstream to CSP-2
CSP-2 and gets confirmation that the account was successfully and gets confirmation that the account was successfully removed.
removed. After receiving the confirmation from CSP-2, CSP-1 After receiving the confirmation from CSP-2, CSP-1 finalizes the
finalizes the deletion operation and sends an acknowledgment to the deletion operation and sends an acknowledgment to the requesting ECS.
requesting ECS.
This use case highlights how different CSPs may implement different This use case highlights how different CSPs may implement different
operational semantics behind the same SCIM operation. Note CSP-1 operational semantics behind the same SCIM operation. Note CSP-1
suspends the account representation for its service where as CPS-2 suspends the account representation for its service, whereas CPS-2
implements a true delete operation. implements a true delete operation.
2.3.4. CSP->CSP - SSO Trigger (Push) 2.3.4. CSP->CSP: SSO Trigger (Push)
In this scenario two CSPs (CSP-1 & CSP-2) have a shared service In this scenario, two CSPs (CSP-1 and CSP-2) have a shared service
agreement in place that requires the exchange of Cloud Service User agreement in place that requires the exchange of Cloud Service User
(CSU) accounts. However, rather than pre-provisioning accounts from (CSU) accounts. However, rather than pre-provisioning accounts from
CSP-1 to CSP-2, CSP-1 waits for a service access request from the end CSP-1 to CSP-2, CSP-1 waits for a service access request from the end
Cloud Service User (CSU-1) before issuing account creation details to Cloud Service User (CSU-1) before issuing account creation details to
CSP-2. When the CSU completes a SSO transaction from CSP-1 to CSP-2, CSP-2. When the CSU completes a SSO transaction from CSP-1 to CSP-2,
CSP-2 then creates an account for the CSU based on information pushed CSP-2 then creates an account for the CSU based on information pushed
to it from CSP-1. to it from CSP-1.
At the protocol level, this class of scenarios may result in the use At the protocol level, this class of scenarios may result in the use
of common protocol exchange patterns between CSP-1 & CSP-2. of common protocol exchange patterns between CSP-1 and CSP-2.
2.3.5. CSP->CSP - SSO Trigger (Pull) 2.3.5. CSP->CSP: SSO Trigger (Pull)
In this scenario two CSPs (CSP-1 & CSP-2) have a shared service In this scenario, two CSPs (CSP-1 and CSP-2) have a shared service
agreement in place that requires the exchange of Cloud Service User agreement in place that requires the exchange of Cloud Service User
(CSU) accounts. However, rather than pre-provisioning accounts from (CSU) accounts. However, rather than pre-provisioning accounts from
CSP-1 to CSP-2, CSP-2 waits for a service access request from the CSP-1 to CSP-2, CSP-2 waits for a service access request from the
Cloud Service User (CSU-1) before initiating a Pull request to gather Cloud Service User (CSU-1) before initiating a Pull request to gather
information about the CSU sufficient to create a local account. information about the CSU sufficient to create a local account.
At the protocol level, this class of scenarios may result in the use At the protocol level, this class of scenarios may result in the use
of common protocol exchange patterns between CSP-2 & CSP-1. of common protocol exchange patterns between CSP-2 and CSP-1.
2.3.6. CSP->CSP - Password Reset (Push) 2.3.6. CSP->CSP: Password Reset (Push)
In this scenario two CSPs (CSP-1 & CSP-2) have a shared service In this scenario, two CSPs (CSP-1 and CSP-2) have a shared service
agreement in place that requires the exchange of Cloud Service User agreement in place that requires the exchange of Cloud Service User
(CSU) accounts. CSP-1 wants to change the password for a specific (CSU) accounts. CSP-1 wants to change the password for a specific
Cloud Service User (CSU-1). CSP-1 sends a request to CSP-2 to reset Cloud Service User (CSU-1). CSP-1 sends a request to CSP-2 to reset
the password value for CSU-1. the password value for CSU-1.
At the protocol level, this scenario may result in the same protocol At the protocol level, this scenario may result in the same protocol
exchange as any other attribute change request. exchange as any other attribute change request.
2.4. Enterprise Cloud Subscriber to Cloud Service Provider 2.4. Flows from Enterprise Cloud Subscriber to Cloud Service Provider
Flows(ECS->CSP) (ECS->CSP)
These scenarios represent flows between an Enterprise Cloud These scenarios represent flows between an Enterprise Cloud
Subscriber (ECS) and a Cloud Service Providers (CSP). It is assumed Subscriber (ECS) and a Cloud Service Providers (CSP). It is assumed
that both the ECS and the CSP maintains an information access service that the ECS and the CSP each maintain an information access service
for the relevant Cloud Service Users (CSUs). These scenarios address for the relevant Cloud Service Users (CSUs). These scenarios address
various joiner, mover, leaver and JIT triggers, resulting in push and various joiner, mover, leaver, and JIT triggers, resulting in push
pull data exchanges between the ECS and the CSP. and pull data exchanges between the ECS and the CSP.
Many of these scenarios are very similar to those defined in the Many of these scenarios are very similar to those defined in
Cloud Service Provider to Cloud Service Provider section above. They Section 2.3. They are identified separately here so that we may
are identified separately here so that we may explore any differences explore any differences that might emerge.
and might emerge.
2.4.1. ECS->CSP - Create Identity (Push) 2.4.1. ECS->CSP: Create Identity (Push)
In this scenario an Enterprise Cloud Subscriber (ECS-1) maintains a In this scenario, an Enterprise Cloud Subscriber (ECS-1) maintains a
service with a Cloud Service Provider (CSP-1) that requires the service with a Cloud Service Provider (CSP-1) that requires the
sharing of various Cloud Service User (CSU) accounts. A new user sharing of various Cloud Service User (CSU) accounts. A new user
joins ECS-1 and so ECS-1 pushes an account creation request to CSP-1, joins ECS-1 and so ECS-1 pushes an account creation request to CSP-1,
supplying all required base SCIM schema attribute values and supplying all required attribute values for the base SCIM schema and
additional extended SCIM schema values as required. additional values for the extended SCIM schema as required.
2.4.2. ECS ->CSP - Update Identity (Push) 2.4.2. ECS->CSP: Update Identity (Push)
In this scenario an Enterprise Cloud Subscriber (ECS-1) maintains a In this scenario, an Enterprise Cloud Subscriber (ECS-1) maintains a
service with Cloud Service Provider (CSP-1) that drives service service with Cloud Service Provider (CSP-1) that drives service
definition from a key account schema attribute called Department. definition from a key account schema attribute called Department.
ECS-1 wishes to move a given CSU from Department A to Department B ECS-1 wishes to move a given CSU from Department A to Department B
and so it pushes an attribute update request to the CSP. and so it pushes an attribute update request to the CSP.
2.4.3. ECS ->CSP - Delete Identity (Push) 2.4.3. ECS->CSP: Delete Identity (Push)
In this scenario an Enterprise Cloud Subscriber (ECS-1) maintains a In this scenario, an Enterprise Cloud Subscriber (ECS-1) maintains a
service with a Cloud Service Provider (CSP-1). Upon termination of service with a Cloud Service Provider (CSP-1). Upon termination of
one of its employees' employment agreement, ECS-1 sends a suspend one of its employee's employment agreement, ECS-1 sends a suspend
account request to CSP-1 (Figure 1.4.3-1). One week later the ECS account request to CSP-1. One week later, the ECS wishes to complete
wishes to complete the process by fully removing the Cloud Service the process by fully removing the Cloud Service User (CSU) account,
User (CSU) account and so it sends a terminate account request to so it sends a terminate account request to CSP-1.
CSP-1.
2.4.4. ECS ->CSP - SSO Pull 2.4.4. ECS->CSP: SSO Trigger (Pull)
In this scenario an Enterprise Cloud Subscriber (ECS-1) maintains a In this scenario, an Enterprise Cloud Subscriber (ECS-1) maintains a
service with a Cloud Service Provider (CSP-1). No accounts are service with a Cloud Service Provider (CSP-1). No accounts are
created or exchanged in advance. However, rather than pre- created or exchanged in advance. However, rather than pre-
provisioning accounts from ECS-1 to CSP-1, CSP-1 waits for a service provisioning accounts from ECS-1 to CSP-1, CSP-1 waits for a service
access request from the Cloud Service User (CSU-1) under the control access request from the Cloud Service User (CSU-1) under the control
domain of ECS-1, before issuing an account Pull request to ECS-1. domain of ECS-1, before issuing an account Pull request to ECS-1.
3. SCIM Use Cases 3. SCIM Use Cases
This section lists the SCIM use cases. This section lists the SCIM use cases.
3.1. Migration of the identities 3.1. Migration of the Identities
Description: Description:
A company SomeEnterprise runs an application ManageThem that relies A company SomeEnterprise runs an application ManageThem that relies
on the identity information about its employees (e.g., identifiers, on the identity information about its employees (e.g., identifiers,
attributes). The identity information is stored at the cloud attributes). The identity information is stored at the cloud
provided by SomeCSP. SomeEnterprise has decided to move identity provided by SomeCSP. SomeEnterprise has decided to move identity
information to the cloud of a different provider - AnotherCSP. In information to the cloud of a different provider -- AnotherCSP. In
addition, SomeEnterprise has purchased a second application addition, SomeEnterprise has purchased a second application
ManageThemMore, which also relies on the identity information. ManageThemMore, which also relies on the identity information.
SomeEnterprise is able to move identity information to AnotherCSP SomeEnterprise is able to move identity information to AnotherCSP
without changing the format of identity information. The application without changing the format of identity information. The application
ManageThemMore is able to use the identity information. ManageThemMore is able to use the identity information.
Pre-conditions: Pre-conditions:
o SomeCSP is a cloud service provider for SomeEnterprise. o SomeCSP is a cloud service provider for SomeEnterprise.
skipping to change at page 11, line 21 skipping to change at page 12, line 26
o SomeEnterprise has moved its employees' identity information from o SomeEnterprise has moved its employees' identity information from
SomeCSP to AnotherCSP without making any changes to representation SomeCSP to AnotherCSP without making any changes to representation
of identity information. of identity information.
o Application ManageThemMore is able to use the identity o Application ManageThemMore is able to use the identity
information. information.
Requirements: Requirements:
o SomeEnterprise, the applications ManageThem and ManageThemMore, o SomeEnterprise, the applications ManageThem and ManageThemMore,
the providers SomeCSP and AnotherCSP support a common standard for and the providers SomeCSP and AnotherCSP support a common standard
identity information, which specifies the following: for identity information, which specifies the following:
* Format (or schema) for representing user identity information * Format (or schema) for representing user identity information
* Interfaces and protocol for managing user identity information * Interfaces and protocol for managing user identity information
o Cloud providers shall be able to meet regulatory requirements when o Cloud providers shall be able to meet regulatory requirements when
migrating identity information between jurisdictional regions migrating identity information between jurisdictional regions
(countries, state-by-state for regulations on privacy). (e.g., countries and states may have differing regulations on
privacy).
o Cloud providers shall be able to log all actions related to o Cloud providers shall be able to log all actions related to
SomeEnterprise employees' identities. SomeEnterprise employees' identities.
o The logs should be secure and available for auditing. o The logs should be secure and available for auditing.
3.2. Single Sign-On (SSO) Service 3.2. Single Sign-On (SSO) Service
Description: Description:
Bob has an account with application hosted by a cloud service Bob has an account in an application hosted by a cloud service
provider SomeCSP. SomeCSP has federated its user identities with a provider SomeCSP. SomeCSP has federated its user identities with a
cloud service provider AnotherCSP. Bob requests a service from an cloud service provider AnotherCSP. Bob requests a service from an
application running on AnotherCSP. The application running on application running on AnotherCSP. The application running on
AnotherCSP, relying on Bob's authentication by SomeCSP and using AnotherCSP, relying on Bob's authentication by SomeCSP and using
identity information provided by SomeCSP, serves Bob's request. identity information provided by SomeCSP, serves Bob's request.
Pre-conditions: Pre-conditions:
o Bob's identity information is stored on SomeCSP. o Bob's identity information is stored on SomeCSP.
skipping to change at page 13, line 5 skipping to change at page 14, line 9
o AnotherCSP must be able to verify the identity information o AnotherCSP must be able to verify the identity information
provided by SomeCSP. provided by SomeCSP.
o SomeCSP must be able to process the identity information received o SomeCSP must be able to process the identity information received
from AnotherCSP. from AnotherCSP.
o SomeCSP and AnotherCSP must log information generated by Bob's o SomeCSP and AnotherCSP must log information generated by Bob's
actions according to their policies and the trust agreement actions according to their policies and the trust agreement
between them. between them.
3.3. Provisioning of the user accounts for a Community of Interest 3.3. Provisioning of the User Accounts for a Community of Interest
(CoI) (COI)
Description: Description:
Organization YourHR provides Human Resources (HR) services to a Organization YourHR provides Human Resources (HR) services to a
Community of Interest (CoI) YourCoI. The HR services are offered as Community of Interest (COI) YourCOI. The HR services are offered as
Software-as-a-Service (SaaS) on public and private clouds. YourCoI's Software as a Service (SaaS) on public and private clouds. YourCOI's
offices are located all over the world. Their Information Technology offices are located all over the world. Their Information Technology
(IT) systems may be composed of the combinations of the applications (IT) systems may be composed of combinations of the applications
running on Private and Public clouds along with the traditional IT running on private and public clouds along with traditional IT
systems. The local YourCoI offices are responsible for collecting systems. The local YourCOI offices are responsible for collecting
personal information(i.e. user identities and attributes). YourHR personal information (i.e., user identities and attributes). YourHR
services provide means for provisioning and distributing the employee services provide means for provisioning and distributing the employee
identity information across all YourCoI offices. YourHR also enables identity information across all YourCOI offices. YourHR also enables
the individual users (e.g., employees) to manage their personal individual users (e.g., employees) to manage personal information
information that they are responsible for (e.g., update of an address that they are responsible for (e.g., update of an address or a
or a telephone number). telephone number).
Pre-conditions: Pre-conditions:
o YourCoI has a complex infrastructure composed of the large number o YourCOI has a complex infrastructure composed of a large number of
of local offices that rely on the diverse IT systems. local offices that rely on diverse IT systems.
o YourCoI has contracted YourHR to provide the HR services. o YourCOI has contracted YourHR to provide the HR services.
o Each local office has a right to establish a personal account for o Each local office has a right to establish a personal account for
an employee. an employee.
Post-conditions: Post-conditions:
o All personal accounts are globally available to any authorized o All personal accounts are globally available to any authorized
user or application across the YourCoI system through the services user or application across the YourCOI system through the services
provided by YourHR. provided by YourHR.
o The employees have ability to manage the part of personal o The employees have the ability to manage the part of personal
information that is in their responsibility. information that is their responsibility.
Requirements: Requirements:
o Your HR must ensure that information generated by the local o YourHR must ensure that the local offices generate information
offices is provisioned securely and considers privacy requirements that is provisioned securely and consider privacy requirements in
in a timely fashion across systems that may span technical (e.g., a timely fashion across systems that may span technical (e.g.,
protocols and applications), administrative (e.g., corporate), protocols and applications), administrative (e.g., corporate),
regulatory (e.g. location) and jurisdictional domains. regulatory (e.g., location), and jurisdictional domains.
o Management of personal information must be protected against o Management of personal information must be protected against
unauthorized access, eavesdropping, and should be distributed only unauthorized access and eavesdropping, and it should be
to authorized parties and services. distributed only to authorized parties and services.
o Regulatory requirements shall be met when migrating identity o Regulatory requirements shall be met when migrating identity
information between jurisdictional regions (countries, state-by- information between jurisdictional regions (e.g., countries and
state for regulations on privacy). states may have differing regulations on privacy).
o All operation with identity data must be securely logged. o All operations with identity data must be securely logged.
o The logs should be available for auditing. o The logs should be available for auditing.
3.4. Transfer of attributes to a relying party web site 3.4. Transfer of Attributes to a Relying Party's Website
Description: Description:
An end user has an account in a directory service A with one or more An end user has an account in a directory service A with one or more
attributes. That user then visits relying party web site B, and the attributes. That user then visits the website of relying party B,
web site B requires attributes of the user. The user selectes some and the website requires attributes of the user. The user selects
attributes and authorizes the transfer of data via authorization some attributes and authorizes the transfer of data via authorization
protocols (e.g. OAuth, SAML), so selected attributes of the user are protocols (e.g., OAuth, SAML), so selected attributes of the user are
transferred from the user's account in directory service A to the web transferred from the user's account in directory service A to the
site B at the time of the user's first visit to that site. website of replying party B at the time of the user's first visit to
that site.
Pre-conditions: Pre-conditions:
o User has an account in a directory service A. o User has an account in directory service A.
o User has one or more attributes. o User has one or more attributes.
o User visits web site of a relying party B. o User visits website of relying party B.
Post-conditions: Post-conditions:
Selected attributes of the user are transferred from the user's Selected attributes of the user are transferred from the user's
account in directory service A to the web site B at the time of the account in directory service A to the website of relying party B at
user's first visit to that site. the time of the user's first visit to that site.
Requirements: Requirements:
o Relying party B must be able to authenticate the end user. o Relying party B must be able to authenticate the end user.
o Relying party B must be able to securely provide the o Relying party B must be able to securely provide the
authentication results to directory service A. authentication results to directory service A.
o Directory service A must be able to securely provide end user's o Directory service A must be able to securely provide end user's
identity information (e.g., attributes) to relying party B. identity information (e.g., attributes) to relying party B.
o Regulatory requirements shall be met when migrating identity o Regulatory requirements shall be met when migrating identity
information between jurisdictional regions (countries, state-by- information between jurisdictional regions (e.g., countries and
state for regulations on privacy). states may have differing regulations on privacy).
o Relying parties have to be aware of changes to their cached copy, o Relying parties have to be aware of changes to their cached copy,
as these would potentially cause a state change in other relying as these would potentially cause a state change in other relying
parties. parties.
o A maximum period should be set for the relying party to cache the o A maximum period should be set for the relying party to cache the
information. information.
3.5. Change notification 3.5. Change Notification
Description: Description:
An end user has an account in a directory service A with one or more An end user has an account in a directory service A with one or more
attributes. That user then visits relying party web site B. Relying attributes. That user then visits the web site of relying party B.
party web site B queries directory service A for attributes The website of relying party B queries directory service A for
associated with that user, and related resources. attributes associated with that user, and related resources.
The attributes of the user change later in directory service A. For The attributes of the user change later in directory service A. For
example, the attributes might change if the user changes their name, example, the attributes might change if the user changes their name,
has their account disabled, or terminates their relationship with has their account disabled, or terminates their relationship with
directory service A. Furthermore, other resources and their directory service A. Furthermore, other resources and their
attributes might also change. The directory service A then wishes to attributes might also change. The directory service A then wishes to
notify relying party web site B of these changes, as relying party B notify the website of relying party B of these changes, as relying
might (or might not) have a cache of those attributes, and if the party B might (or might not) have a cache of those attributes, and if
relying party B were aware of these changes to their cached copy, relying party B were aware of these changes to their cached copy, it
would potentially cause a state change in relying party B. would potentially cause a state change in relying party B.
The volume of changes, however, might be substantial, and only some The volume of changes, however, might be substantial, and only some
of the changes may be of interest to relying party B, so directory of the changes may be of interest to relying party B, so directory
service A does not wish to "push" all the changes to B. Instead, service A does not wish to "push" all the changes to B. Instead,
directory service A wishes to notify B that there are changes directory service A wishes to notify B that there are changes
potentially of interest, such that B can at an appropriate time potentially of interest, such that B can at an appropriate time
subsequently contact directory service A and retrieve just the subset subsequently contact directory service A and retrieve just the subset
of changes of interest to B. of changes of interest to B.
Note that the user must authorize the directory service A to transfer Note that the user must authorize directory service A to transfer
data to the web site, and the user must authorize the directory data to the website, and the user must authorize directory service A
service A to notify the web site. to notify the website.
Pre-conditions: Pre-conditions:
o User has an account in a directory service A. o User has an account in directory service A.
o User has one or more attributes. o User has one or more attributes.
o User visits relying party web site B. o User visits the website of relying party B.
o The resource being updated is at the web site. o The resource being updated is at the website.
Post-conditions: Post-conditions:
Directory service A is able to notify relying party B that there are Directory service A is able to notify relying party B that there are
changes potentially of interest. changes potentially of interest.
Requirements: Requirements:
o Relying party B must be able to authenticate the end user. o Relying party B must be able to authenticate the end user.
skipping to change at page 16, line 27 skipping to change at page 17, line 39
authentication results to directory service A. authentication results to directory service A.
o Directory service A must be able to securely provide end user's o Directory service A must be able to securely provide end user's
changed identity information (e.g., attributes) to relying party changed identity information (e.g., attributes) to relying party
B. B.
o Relying party B must be able at an appropriate time to o Relying party B must be able at an appropriate time to
subsequently contact directory service A and retrieve just the subsequently contact directory service A and retrieve just the
subset of changes of interest to relying party B. subset of changes of interest to relying party B.
4. Security considerations 4. Security Considerations
Authentication and authorization must be guaranteed for the SCIM Authentication and authorization must be guaranteed for the SCIM
operations, to ensure that only authenticated entities can perform operations to ensure that only authenticated entities can perform the
the SCIM requests and the requested SCIM operations are authorized. SCIM requests and the requested SCIM operations are authorized.
SCIM resources (e.g., Users and Groups) can contain sensitive SCIM resources (e.g., Users and Groups) can contain sensitive
information. Thus, data confidentiality MUST be guaranteed at the information. Thus, data confidentiality MUST be guaranteed at the
transport layer. transport layer.
There can be privacy issues that go beyond transport security, e.g. There can be privacy issues that go beyond transport security, e.g.,
moving PII offshore between CSPs. Regulatory requirements shall be moving personally identifying information (PII) offshore between
met when migrating identity information between jurisdictional CSPs. Regulatory requirements shall be met when migrating identity
regions (countries, state-by-state for regulations on privacy. information between jurisdictional regions (e.g., countries and
states may have differing regulations on privacy).
Additionally, privacy sensitive data elements may be omitted or Additionally, privacy-sensitive data elements may be omitted or
obscured in SCIM transactions or stored records to protect these data obscured in SCIM transactions or stored records to protect these data
elements for a user. For instance a role based identifier might be elements for a user. For instance, a role-based identifier might be
used in place of an individual's name. used in place of an individual's name.
Detailed security considerations are specified in section 7 of SCIM Detailed security considerations are specified in Section 7 of the
protocol [I-D.ietf-scim-api] and section 9 of SCIM schema SCIM protocol [RFC7644] and Section 9 of the SCIM schema [RFC7643].
[I-D.ietf-scim-core-schema].
5. IANA considerations
This Internet Draft includes no request to IANA.
6. Acknowledgements 5. References
Authors would like to thank Ray Counterman, Richard Fiekowsky, Bert 5.1. Normative References
Greevenbosch, Barry Leiba, Kelly Grizzle, Magnus Nystrom, Stephen
Farrell, Kathleen Moriarty, Benoit Claise, Dapeng Liu and Jun Li for
their reviews and comments.
Also thanks to Darran Rolls and Patrick Harding, the SCIM user [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
scenarios section is taken from them. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
7. References 5.2. Informative References
7.1. Normative References [RFC7643] Hunt, P., Ed., Grizzle, K., Wahlstroem, E., and
C. Mortimore, "System for Cross-domain Identity
Management: Core Schema", RFC 7643, DOI 10.17487/RFC7643,
September 2015, <http://www.rfc-editor.org/info/rfc7643>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC7644] Hunt, P., Ed., Grizzle, K., Ansari, M., Wahlstroem, E.,
Requirement Levels", BCP 14, RFC 2119, March 1997. and C. Mortimore, "System for Cross-domain Identity
Management: Protocol", RFC 7644, DOI 10.17487/RFC7644,
September 2015, <http://www.rfc-editor.org/info/rfc7644>.
7.2. Informative References Acknowledgments
[I-D.ietf-scim-api] The authors would like to thank Ray Counterman, Richard Fiekowsky,
Hunt, P., Grizzle, K., Ansari, M., Wahlstroem, E., and C. Bert Greevenbosch, Barry Leiba, Kelly Grizzle, Magnus Nystrom,
Mortimore, "System for Cross-Domain Identity Management: Stephen Farrell, Kathleen Moriarty, Benoit Claise, Dapeng Liu, and
Protocol", draft-ietf-scim-api-17 (work in progress), Jun Li for their reviews and comments.
April 2015.
[I-D.ietf-scim-core-schema] Also, thanks to Darran Rolls and Patrick Harding; Section 2 ("SCIM
Hunt, P., Grizzle, K., Wahlstroem, E., and C. Mortimore, User Scenarios") is taken from them.
"System for Cross-Domain Identity Management: Core
Schema", draft-ietf-scim-core-schema-18 (work in
progress), April 2015.
Authors' Addresses Authors' Addresses
Kepeng LI (editor) Kepeng LI (editor)
Alibaba Group Alibaba Group
Wenyixi Road, Yuhang District 969 Wenyixi Road, Yuhang District
Hangzhou, Zhejiang 311121 Hangzhou, Zhejiang 311121
China China
Email: kepeng.lkp@alibaba-inc.com Email: kepeng.lkp@alibaba-inc.com
Phil Hunt Phil Hunt
Oracle Oracle
Email: phil.hunt@oracle.com Email: phil.hunt@oracle.com
Bhumip Khasnabish Bhumip Khasnabish
ZTE (TX) Inc. ZTE (TX) Inc.
55 Madison Ave, Suite 302 55 Madison Ave, Suite 302
Morristown, New Jersey 07960 Morristown, New Jersey 07960
USA United States
Phone: +001-781-752-8003 Phone: +001-781-752-8003
Email: vumip1@gmail.com, bhumip.khasnabish@ztetx.com Email: vumip1@gmail.com, bhumip.khasnabish@ztetx.com
URI: http://tinyurl.com/bhumip/ URI: http://tinyurl.com/bhumip/
Anthony Nadalin Anthony Nadalin
Microsoft Microsoft
Email: tonynad@microsoft.com Email: tonynad@microsoft.com
 End of changes. 129 change blocks. 
297 lines changed or deleted 293 lines changed or added

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