--- 1/draft-ietf-scim-use-cases-06.txt 2015-05-02 10:14:51.827331672 -0700 +++ 2/draft-ietf-scim-use-cases-07.txt 2015-05-02 10:14:51.863332554 -0700 @@ -1,49 +1,49 @@ -SCIM WG P. Hunt -Internet-Draft Oracle -Intended status: Informational B. Khasnabish -Expires: October 15, 2015 ZTE (TX) Inc. +SCIM WG K. LI, Ed. +Internet-Draft Alibaba Group +Intended status: Informational P. Hunt +Expires: November 3, 2015 Oracle + B. Khasnabish + ZTE (TX) Inc. A. Nadalin Microsoft - K. LI, Ed. - Alibaba Group Z. Zeltsan Individual - April 13, 2015 + May 2, 2015 - SCIM Definitions, Overview, and Flows - draft-ietf-scim-use-cases-06 + SCIM Definitions, Overview, Concepts and Requirements + draft-ietf-scim-use-cases-07 Abstract This document provides definitions and an overview of the System for Cross-domain Identity Management (SCIM). It lays out the system's - models and flows, and includes user scenarios, use cases, and - requirements. + concepts, models and flows, and includes user scenarios, use cases, + and requirements. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on October 15, 2015. + This Internet-Draft will expire on November 3, 2015. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -64,50 +64,55 @@ 2.2.2. Actors . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2.3. Modes & Flows . . . . . . . . . . . . . . . . . . . . 6 2.2.4. Bulk & Batch Operational Semantics . . . . . . . . . . 7 2.3. Cloud Service Provider to Cloud Service Provider Flows (CSP->CSP) . . . . . . . . . . . . . . . . . . . . . . . . 7 2.3.1. CSP->CSP - Create Identity (Push) . . . . . . . . . . 7 2.3.2. CSP->CSP - Update Identity (Push) . . . . . . . . . . 7 2.3.3. CSP->CSP - Delete Identity (Push) . . . . . . . . . . 8 2.3.4. CSP->CSP - SSO Trigger (Push) . . . . . . . . . . . . 8 2.3.5. CSP->CSP - SSO Trigger (Pull) . . . . . . . . . . . . 8 - 2.3.6. CSP->CSP - Password Reset (Push) . . . . . . . . . . . 8 + 2.3.6. CSP->CSP - Password Reset (Push) . . . . . . . . . . . 9 2.4. Enterprise Cloud Subscriber to Cloud Service Provider Flows(ECS->CSP) . . . . . . . . . . . . . . . . . . . . . 9 2.4.1. ECS->CSP - Create Identity (Push) . . . . . . . . . . 9 2.4.2. ECS ->CSP - Update Identity (Push) . . . . . . . . . . 9 - 2.4.3. ECS ->CSP - Delete Identity (Push) . . . . . . . . . . 9 + 2.4.3. ECS ->CSP - Delete Identity (Push) . . . . . . . . . . 10 2.4.4. ECS ->CSP - SSO Pull . . . . . . . . . . . . . . . . . 10 3. SCIM Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 10 - 3.1. Change of the ownership of a file . . . . . . . . . . . . 10 - 3.2. Migration of the identities . . . . . . . . . . . . . . . 11 - 3.3. Single Sign-On (SSO) Service . . . . . . . . . . . . . . . 12 - 3.4. Provisioning of the user accounts for a Community of + 3.1. Migration of the identities . . . . . . . . . . . . . . . 10 + 3.2. Single Sign-On (SSO) Service . . . . . . . . . . . . . . . 11 + 3.3. Provisioning of the user accounts for a Community of Interest (CoI) . . . . . . . . . . . . . . . . . . . . . . 13 - 3.5. Transfer of attributes to a relying party web site . . . . 14 - 3.6. Change notification . . . . . . . . . . . . . . . . . . . 15 + 3.4. Transfer of attributes to a relying party web site . . . . 14 + 3.5. Change notification . . . . . . . . . . . . . . . . . . . 15 4. Security considerations . . . . . . . . . . . . . . . . . . . 16 - 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 17 + 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 16 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7.1. Normative References . . . . . . . . . . . . . . . . . . . 17 7.2. Informative References . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 1. Introduction - This document provides the SCIM definitions, models, flows, scenarios - and use cases. It also provides a list of the requirements derived - from the use cases. 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 protocol [I-D.ietf-scim-api]. + This document provides the SCIM definitions, overview, concepts, + flows, scenarios and use cases. It also provides a list of the + requirements derived from the use cases. + + 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 + protocol [I-D.ietf-scim-api]. + + Unlike the practice of some protocols like ABFAB and SAML2 WebSSO, + SCIM provides provisioning and de-provisioning of resources in a + separate context from authentication (aka just-in-time provisioning). 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] when they appear in ALL CAPS. These words may also appear in this document in lower case as plain English words, absent their normative meanings. Here is a list of acronyms and abbreviations used in this document: @@ -128,51 +133,52 @@ o JIT: Just In Time o PaaS: Platform as a Service o SaaS: Software as a Service o SAML: Security Assertion Markup Language o SCIM: System for Cross-domain Identity Management - o SSO: Single-Sign On 2. SCIM User Scenarios 2.1. Background & Context The System for Cross-domain Identity Management (SCIM) specification - is designed to make managing user identity in cloud based - applications and services easier. The specification suite seeks to - build upon experience with existing schemas and deployments, placing - specific emphasis on simplicity of development and integration, while - applying existing authentication, authorization, and privacy models. - It's intent is to reduce the cost and complexity of user management - operations by providing a common user schema and extension model, as - well as binding documents to provide patterns for exchanging this - schema using standard protocols. In essence, make it fast, cheap, - and easy to move users in to, out of, and around the cloud. + is designed to manage user identity in cloud based applications and + services in a standardized way to enable interoperability, security + and scalability. The specification suite seeks to build upon + experience with existing schemas and deployments, placing specific + emphasis on simplicity of development and integration, while applying + existing authentication, authorization, and privacy models. The + intent of SCIM specification is to reduce the cost and complexity of + user management operations by providing a common user schema and + extension model, as well as binding documents to provide patterns for + exchanging this schema using standard protocols. In essence, make it + fast, cheap, and easy to move users in to, out of, and around the + cloud. The SCIM scenarios are overview user stories designed to help clarify the intended scope of the SCIM effort. 2.2. Model Concepts 2.2.1. Triggers Quite simply, triggers are actions or activities that start SCIM flows. Triggers may not be relevant at the protocol or the schema, they really serve to help identify the type or activity that resulted in a SCIM protocol exchange. Triggers make use of the traditional - provisioning C.R.U.D (Create Read Update & Delete) operations but add + provisioning CRUD (Create Read Update & Delete) operations but add additional use case contexts like "SSO" (Single-Sign On) as it is designed to capture a class of use case that makes sense to the actor requesting it rather than to describe a protocol operation. o Create SCIM Identity Resource - Service On-boarding Trigger: A "create SCIM identity resource" trigger is a service on-boarding activity in which a business action such as a new hire or new service subscription is initiated by one of the SCIM Actors. In the protocol itself, service on-boarding may well be implemented via the same resource PUT method as a service change. This is @@ -191,55 +197,56 @@ o Delete SCIM Identity Resource - Service Termination Trigger: A "delete SCIM identity resource" trigger represents a specific and deliberate action to remove an identity from a given SCIM service point. At this stage it is unclear if the SCIM protocol needs to identify separate protocol exchange for a service suspension actions. This may be relevant as target services usually differentiate between these result and may require separate resource representations as a result. - o Single-Sign On (SSO) Trigger - Real-time Service Access Request: A - "Single-Sign On" trigger is a special class of activity in which a - Create or Update trigger is initiated during an SSO operational - flow. The implication here is that as the result of a real-time - service access request by the end user (SSO), defined SCIM - protocol exchanges can be used to initiate SCIM resource CRUD - somewhere in the service cloud. + o Single-Sign On (SSO) Trigger - Service Access Request: A "Single- + Sign On" trigger is a special class of activity in which a Create + or Update trigger is initiated during an SSO operational flow. + The implication here is that as the result of a service access + request by the end user (SSO), defined SCIM protocol exchanges can + be used to initiate SCIM resource CRUD somewhere in the service + cloud. 2.2.2. Actors Actors are the operating parties that take part in both sides of a SCIM protocol exchange, and help identify the source of a given Trigger. So far, we have identified the following SCIM Actors: o Cloud Service Provider (CSP): A CSP is the entity operating a given cloud service. In a SaaS scenario this is simply the application provider. In an IaaS or PaaS scenario, the CSP may be the underlying IaaS/PaaS infrastructure provider or the owner of the application running on that platform. In all cases, the CSP is the thing that holds the identity information being operated upon. Put another way, the CSP really is the service that the end-end user interacts with. o Enterprise Cloud Subscriber (ECS): An ECS represents a middle-tier of aggregation for related identity records. In one of our sample - enterprise SaaS scenarios, the ECS is "FooBar.Inc" that subscribes - to a cloud based CRM service service "SaaS-CRM.Inc" (the CSP) for - all of its sales staff. The actual Cloud Service Users (CSUs) are - the FooBar.Inc. sales staff. The ECS actor is identified to help - capture use cases in which a single entity is given administrative - responsibility for other identity accounts. SCIM may not address - the configuration and setup of an ECS within the CSP, but it does - address use cases in which SCIM identity resources are grouped - together and administers as part of some broader agreement or - operational exchange. + enterprise SaaS scenarios, the ECS is "Example.com" that + subscribes to a cloud based CRM service service "SaaS-CRM.Inc" + (the CSP) for all of its sales staff. The actual Cloud Service + Users (CSUs) are the FooBar.Inc. sales staff. The ECS actor is + identified to help capture use cases in which a single entity is + given administrative responsibility for other identity accounts. + + SCIM may not address the configuration and setup of an ECS within + the CSP, but it does address use cases in which SCIM identity + resources are grouped together and administers as part of some + broader agreement or operational exchange. o Cloud Service User (CSU): A CSU represents the real cloud service end user - the "person logging into and using the cloud service". As described above, and ECS will typically own or manage multiple CSU identities where as the CSU represents the FooBar.Inc. employee using the cloud service to manage their CRM process. +---------------------+ | Cloud Service | | Provider (CSP) | @@ -353,21 +360,21 @@ In this scenario two CSPs (CSP-1 & CSP-2) have a shared service agreement in place that requires the exchange of Cloud Service User (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 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 then creates an account for the CSU based on information pushed to it from CSP-1. At the protocol level, this class of scenarios may result in the use - of common protocol exchange patters between CSP-1 & CSP-2. + of common protocol exchange patterns between CSP-1 & CSP-2. 2.3.5. CSP->CSP - SSO Trigger (Pull) In this scenario two CSPs (CSP-1 & CSP-2) have a shared service agreement in place that requires the exchange of Cloud Service User (CSU) accounts. However, rather than pre-provisioning accounts from 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 information about the CSU sufficient to create a local account. @@ -383,24 +390,24 @@ the password value for CSU-1. At the protocol level, this scenario may result in the same protocol exchange as any other attribute change request. 2.4. Enterprise Cloud Subscriber to Cloud Service Provider Flows(ECS->CSP) These scenarios represent flows between an Enterprise Cloud Subscriber (ECS) and a Cloud Service Providers (CSP). It is assumed - that both the ECS and the CSP maintains an LDAP service for the - relevant Cloud Service Users (CSUs). These scenarios address various - joiner, mover, leaver and JIT triggers, resulting in push and pull - data exchanges between the ECS and the CSP. + that both the ECS and the CSP maintains an information access service + for the relevant Cloud Service Users (CSUs). These scenarios address + various joiner, mover, leaver and JIT triggers, resulting in push and + pull data exchanges between the ECS and the CSP. Many of these scenarios are very similar to those defined in the Cloud Service Provider to Cloud Service Provider section above. They are identified separately here so that we may explore any differences and might emerge. 2.4.1. ECS->CSP - Create Identity (Push) In this scenario an Enterprise Cloud Subscriber (ECS-1) maintains a service with a Cloud Service Provider (CSP-1) that requires the @@ -433,70 +440,21 @@ service with a Cloud Service Provider (CSP-1). No accounts are created or exchanged in advance. However, rather than pre- 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 domain of ECS-1, before issuing an account Pull request to ECS-1. 3. SCIM Use Cases This section lists the SCIM use cases. -3.1. Change of the ownership of a file - - Description: - - Bob - an employee of the company SomeEnterprise - creates a file, - which is located at the cloud provided by SomeCSP. After Bob leaves - SomeEnterprise, SomeCSP on a request from SomeEnterprise terminates - Bob's rights to the file and transfers his former rights to Bill - - another employee of SomeEnterprise. - - Pre-conditions: - - o SomeCSP is a cloud service provider for SomeEnterprise. - - o With permission of SomeEnterprise, Bob had created a file at the - cloud provided by SomeCSP. - - o Bob has left SomeEnterprise. - - o SomeEnterprise terminates Bob's rights to the file and, possibly, - decommissions Bob's identity. - - o SomeEnterprise communicates the changes to Bob's rights to - SomeCSP. - - o SomeCSP enforces the changes made by SomeEnterprise. - - o SomeEnterprise requests SomeCSP to transfer Bob's former rights to - Bill. - - Post-conditions: - - o Bob does not have the rights to the file at the cloud provided by - SomeCSP. - - o Bill has the rights to the file that Bob had. - - Requirements: - - o SomeEnterprise can securely communicate to SomeCSP all changes - regarding its employee's identity. - - o SomeCSP can enforce the requested changes. - - o SomeCSP shall be able to log all changes regarding a - SomeEnterprise employee's identity. - - o The logs should be secure and available for auditing. - -3.2. Migration of the identities +3.1. Migration of the identities Description: A company SomeEnterprise runs an application ManageThem that relies on the identity information about its employees (e.g., identifiers, attributes). The identity information is stored at the cloud provided by SomeCSP. SomeEnterprise has decided to move identity information to the cloud of a different provider - AnotherCSP. In addition, SomeEnterprise has purchased a second application ManageThemMore, which also relies on the identity information. @@ -529,26 +487,30 @@ Requirements: o SomeEnterprise, the applications ManageThem and ManageThemMore, the providers SomeCSP and AnotherCSP support a common standard for identity information, which specifies the following: * Format (or schema) for representing user identity information * Interfaces and protocol for managing user identity information + o Cloud providers shall be able to meet regulatory requirements when + migrating identity information between jurisdictional regions + (countries, state-by-state for regulations on privacy). + o Cloud providers shall be able to log all actions related to SomeEnterprise employees' identities. o The logs should be secure and available for auditing. -3.3. Single Sign-On (SSO) Service +3.2. Single Sign-On (SSO) Service Description: Bob has an account with application hosted by a cloud service provider SomeCSP. SomeCSP has federated its user identities with a cloud service provider AnotherCSP. Bob requests a service from an application running on AnotherCSP. The application running on AnotherCSP, relying on Bob's authentication by SomeCSP and using identity information provided by SomeCSP, serves Bob's request. @@ -596,21 +558,21 @@ o AnotherCSP must be able to verify the identity information provided by SomeCSP. o SomeCSP must be able to process the identity information received from AnotherCSP. o SomeCSP and AnotherCSP must log information generated by Bob's actions according to their policies and the trust agreement between them. -3.4. Provisioning of the user accounts for a Community of Interest +3.3. Provisioning of the user accounts for a Community of Interest (CoI) Description: Organization YourHR provides Human Resources (HR) services to a Community of Interest (CoI) YourCoI. The HR services are offered as Software-as-a-Service (SaaS) on public and private clouds. YourCoI's offices are located all over the world. Their Information Technology (IT) systems may be composed of the combinations of the applications running on Private and Public clouds along with the traditional IT @@ -636,40 +598,47 @@ o All personal accounts are globally available to any authorized user or application across the YourCoI system through the services provided by YourHR. o The employees have ability to manage the part of personal information that is in their responsibility. Requirements: - o YourHR must ensure that the personal information generated by the - local offices is timely available in a globally-accessible - database. + o Your HR must ensure that information generated by the local + offices is provisioned securely and considers privacy requirements + in a timely fashion across systems that may span technical (e.g., + protocols and applications), administrative (e.g., corporate), + regulatory (e.g. location) and jurisdictional domains. - o Identity management of the personal data must be protected against - unauthorised access and remain confidential to only authorised - parties. + o Management of personal information must be protected against + unauthorized access, eavesdropping, and should be distributed only + to authorized parties and services. + + o Regulatory requirements shall be met when migrating identity + information between jurisdictional regions (countries, state-by- + state for regulations on privacy). o All operation with identity data must be securely logged. o The logs should be available for auditing. -3.5. Transfer of attributes to a relying party web site +3.4. Transfer of attributes to a relying party web site Description: 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 - user authorizes the transfer of data via authorization protocols - (e.g. OAuth, SAML), so selected attributes of the user are + web site B requires attributes of the user. The user selectes some + attributes and authorizes the transfer of data via authorization + 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 site B at the time of the user's first visit to that site. Pre-conditions: o User has an account in a directory service A. o User has one or more attributes. o User visits web site of a relying party B. @@ -683,28 +652,32 @@ Requirements: o Relying party B must be able to authenticate the end user. o Relying party B must be able to securely provide the authentication results to directory service A. o Directory service A must be able to securely provide end user's identity information (e.g., attributes) to relying party B. + o Regulatory requirements shall be met when migrating identity + information between jurisdictional regions (countries, state-by- + state for regulations on privacy). + o Relying parties have to be aware of changes to their cached copy, as these would potentially cause a state change in other relying parties. o A maximum period should be set for the relying party to cache the information. -3.6. Change notification +3.5. Change notification Description: 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 party web site B queries directory service A for attributes associated with that user, and related resources. The attributes of the user change later in directory service A. For example, the attributes might change if the user changes their name, @@ -761,82 +734,87 @@ 4. Security considerations Authentication and authorization must be guaranteed for the SCIM operations, to ensure that only authenticated entities can perform the SCIM requests and the requested SCIM operations are authorized. SCIM resources (e.g., Users and Groups) can contain sensitive information. Thus, data confidentiality MUST be guaranteed at the transport layer. + There can be privacy issues that go beyond transport security, e.g. + moving PII offshore between CSPs. Regulatory requirements shall be + met when migrating identity information between jurisdictional + regions (countries, state-by-state for regulations on privacy. + Detailed security considerations are specified in section 7 of SCIM protocol [I-D.ietf-scim-api] and section 9 of SCIM schema [I-D.ietf-scim-core-schema]. 5. IANA considerations This Internet Draft includes no request to IANA. 6. Acknowledgements Authors would like to thank Ray Counterman, Richard Fiekowsky, Bert - Greevenbosch, Barry Leiba, Kelly Grizzle, Magnus Nystrom, Dapeng Liu - and Jun Li for their reviews and comments. + 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 scenarios section is taken from them. 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 7.2. Informative References [I-D.ietf-scim-api] Hunt, P., Grizzle, K., Ansari, M., Wahlstroem, E., and C. Mortimore, "System for Cross-Domain Identity Management: - Protocol", draft-ietf-scim-api-16 (work in progress), - March 2015. + Protocol", draft-ietf-scim-api-17 (work in progress), + April 2015. [I-D.ietf-scim-core-schema] Hunt, P., Grizzle, K., Wahlstroem, E., and C. Mortimore, "System for Cross-Domain Identity Management: Core - Schema", draft-ietf-scim-core-schema-17 (work in - progress), March 2015. + Schema", draft-ietf-scim-core-schema-18 (work in + progress), April 2015. Authors' Addresses + Kepeng LI (editor) + Alibaba Group + Wenyixi Road, Yuhang District + Hangzhou, Zhejiang 311121 + China + + Email: kepeng.lkp@alibaba-inc.com Phil Hunt Oracle Email: phil.hunt@oracle.com Bhumip Khasnabish ZTE (TX) Inc. 55 Madison Ave, Suite 302 Morristown, New Jersey 07960 USA Phone: +001-781-752-8003 Email: vumip1@gmail.com, bhumip.khasnabish@ztetx.com URI: http://tinyurl.com/bhumip/ Anthony Nadalin Microsoft Email: tonynad@microsoft.com - Kepeng LI (editor) - Alibaba Group - Wenyixi Road, Yuhang District - Hangzhou, Zhejiang 311121 - China - - Email: kepeng.lkp@alibaba-inc.com - Zachary Zeltsan Individual Email: Zachary.Zeltsan@gmail.com