draft-ietf-scim-use-cases-01.txt   draft-ietf-scim-use-cases-02.txt 
SCIM WG P. Hunt SCIM WG P. Hunt
Internet-Draft Oracle Internet-Draft Oracle
Intended status: Informational B. Khasnabish Intended status: Informational B. Khasnabish
Expires: September 5, 2014 ZTE USA,Inc. Expires: December 20, 2014 ZTE USA,Inc.
A. Nadalin A. Nadalin
Microsoft Microsoft
K. Li K. Li
Huawei Huawei
Z. Zeltsan Z. Zeltsan
Individual Individual
March 4, 2014 June 18, 2014
SCIM Use Cases SCIM Use Cases
draft-ietf-scim-use-cases-01 draft-ietf-scim-use-cases-02
Abstract Abstract
This document lists the user scenarios and use cases of System for This document lists the user scenarios and use cases of System for
Cross-domain Identity Management (SCIM). Cross-domain Identity Management (SCIM).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 September 5, 2014. This Internet-Draft will expire on December 20, 2014.
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 45 skipping to change at page 2, line 45
3.1. Change of the ownership of a file . . . . . . . . . . . . 10 3.1. Change of the ownership of a file . . . . . . . . . . . . 10
3.2. Migration of the identities . . . . . . . . . . . . . . . 11 3.2. Migration of the identities . . . . . . . . . . . . . . . 11
3.3. Single Sign-On (SSO) Service . . . . . . . . . . . . . . 12 3.3. Single Sign-On (SSO) Service . . . . . . . . . . . . . . 12
3.4. Provisioning of the user accounts for a Community of 3.4. Provisioning of the user accounts for a Community of
Interest (CoI) . . . . . . . . . . . . . . . . . . . . . 13 Interest (CoI) . . . . . . . . . . . . . . . . . . . . . 13
3.5. Transfer of attributes to a relying party web site . . . 14 3.5. Transfer of attributes to a relying party web site . . . 14
3.6. Change notification . . . . . . . . . . . . . . . . . . . 15 3.6. Change notification . . . . . . . . . . . . . . . . . . . 15
4. Security considerations . . . . . . . . . . . . . . . . . . . 16 4. Security considerations . . . . . . . . . . . . . . . . . . . 16
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. Normative References . . . . . . . . . . . . . . . . . . 16 7.1. Normative References . . . . . . . . . . . . . . . . . . 17
7.2. Informative References . . . . . . . . . . . . . . . . . 17 7.2. Informative References . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
This document describes the SCIM scenarios and use cases. It also This document describes the SCIM scenarios and use cases. It also
provides a list of the requirements derived from the use cases. The provides a list of the requirements derived from the use cases. The
document's objective is to help with understanding of the design and document's objective is to help with understanding of the design and
applicability of SCIM schema [I-D.ietf-scim-core-schema] and SCIM applicability of SCIM schema [I-D.ietf-scim-core-schema] and SCIM
protocol [I-D.ietf-scim-api]. protocol [I-D.ietf-scim-api].
skipping to change at page 4, line 30 skipping to change at page 4, line 30
The SCIM scenarios are overview user stories designed to help clarify The SCIM scenarios are overview user stories designed to help clarify
the intended scope of the SCIM effort. 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 or the schema,
they really serve to help identity the type or activity that resulted they really serve to help identify the type or activity that resulted
in a SCIM protocol exchange. Triggers make use of the traditional in a SCIM protocol exchange. Triggers make use of the traditional
provisioning C.R.U.D (Create Read Update & Delete) operations but add provisioning C.R.U.D (Create Read Update & Delete) operations but add
additional use case contexts like "SSO" as it is designed to capture additional use case contexts like "SSO" (Single-Sign On) as it is
a class of use case that makes sense to the actor requesting it designed to capture a class of use case that makes sense to the actor
rather than to describe a protocol operation. 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 resource trigger is a service on-boarding activity in "create SCIM identity resource" trigger is a service on-boarding
which a business action such as a new hire or new service activity in which a business action such as a new hire or new
subscription is initiated by one of the SCIM Actors. In the service subscription is initiated by one of the SCIM Actors. In
protocol itself, service on-boarding may well be implemented via the protocol itself, service on-boarding may well be implemented
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 not to the use cases that drive particular to the implementation, and not to the use cases that
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 resource trigger is a service change activity as a result of SCIM identity resource" trigger is a service change activity as a
an identity moving or changing its service level. An Update result of an identity moving or changing its service level. An
Identity trigger might be the result of a change in a service "update SCIM identity" trigger might be the result of a change in
subscription level or a change to key identity data used to denote a service subscription level or a change to key identity data used
a service subscription level. Password changes are specifically to denote a service subscription level. Password changes are
called out from other more general identity attribute changes as specifically called out from other more general identity attribute
they are considered to have specific use case differences. changes as they are considered to have specific use case
differences.
o Delete SCIM Identity Resource - Service Termination Trigger: A o Delete SCIM Identity Resource - Service Termination Trigger: A
delete SCIM resource trigger represents a specific and deliberate "delete SCIM identity resource" trigger represents a specific and
action to remove an identity from a given SCIM service point. At deliberate action to remove an identity from a given SCIM service
this stage it is unclear if the SCIM protocol needs to identify point. At this stage it is unclear if the SCIM protocol needs to
separate protocol exchange for a service suspension actions. This identify separate protocol exchange for a service suspension
may be relevant as target services usually differentiate between actions. This may be relevant as target services usually
these result and may require separate resource representations as differentiate between these result and may require separate
a result. resource representations as a result.
o Single-Sign On (SSO) Trigger - Real-time Service Access Request: A o Single-Sign On (SSO) Trigger - Real-time Service Access Request: A
SSO trigger is a special class of activity in which a Create or "Single-Sign On" trigger is a special class of activity in which a
Update trigger is initiated during an SSO operational flow. The Create or Update trigger is initiated during an SSO operational
implication here is that as the result of a real-time service flow. The implication here is that as the result of a real-time
access request by the end user (SSO), defined SCIM protocol service access request by the end user (SSO), defined SCIM
exchanges can be used to initiate SCIM resource CRUD somewhere in protocol exchanges can be used to initiate SCIM resource CRUD
the service cloud. somewhere in the 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
skipping to change at page 5, line 45 skipping to change at page 5, line 45
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 user interacts with. end-end 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 "FooBar.Inc" that subscribes enterprise SaaS scenarios, the ECS is "FooBar.Inc" that subscribes
to a cloud based CRM service service "SaaS-CRM.Inc" (the CSP) for 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 all of its sales staff. The actual Cloud Service Users (CSUs) are
the FooBar.Inc. sales staff. The ECS actor is identified to help the FooBar.Inc. sales staff. The ECS actor is identified to help
capture use cases in which a single entitle is given capture use cases in which a single entity is given administrative
administrative responsibility for other identity accounts. SCIM responsibility for other identity accounts. SCIM may not address
may not address the configuration and setup of an ECS within the the configuration and setup of an ECS within the CSP, but it does
CSP, but it does address use cases in which SCIM identity address use cases in which SCIM identity resources are grouped
resources are grouped together and administers as part of some together and administers as part of some broader agreement or
broader agreement or operational exchange. 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-end user - the "person logging into and using the cloud end user - the "person logging into and using the cloud service".
service". As described above, and ECS will typically own or As described above, and ECS will typically own or manage multiple
manage multiple CSU identities where as the CSU represents the CSU identities where as the CSU represents the FooBar.Inc.
FooBar.Inc. employee using the cloud service to manage their CRM employee using the cloud service to manage their CRM process.
process.
+---------------------+ +---------------------+
| Cloud Service | | Cloud Service |
| Provider (CSP) | | Provider (CSP) |
+---------------------+ +---------------------+
| |
+--------------------------------+ +--------------------------------+
| | | |
v v v v
+----------------+ +----------------+ +----------------+ +----------------+
skipping to change at page 7, line 4 skipping to change at page 6, line 50
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 & 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 again they help the reader follow the SCIM scenarios and apply them
to real work use cases. to real world use cases.
2.2.4. Bulk & Batch Operational Semantics 2.2.4. Bulk & Batch Operational Semantics
It is assumed that each of the triggers action outlined in this It is assumed that each of the triggers action 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
skipping to change at page 7, line 37 skipping to change at page 7, line 35
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 & 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 down-stream 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 acknowledgement 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 & 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
skipping to change at page 8, line 16 skipping to change at page 8, line 14
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 & 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 down-stream to
CSP-2 and gets confirmation that the account was successfully CSP-2 and gets confirmation that the account was successfully
removed. After receiving the confirmation from CSP-2, CSP-1 sends an removed. After receiving the confirmation from CSP-2, CSP-1
acknowledgment to the requesting ECS. finalizes the deletion operation and sends an acknowledgment to the
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 where as 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 & 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
skipping to change at page 10, line 16 skipping to change at page 10, line 16
User (CSU) account and so it sends a terminate account request to User (CSU) account and 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 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 CSP-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. Change of the ownership of a file 3.1. Change of the ownership of a file
Description: Description:
Bob - an employee of the company SomeEnterprise - creates a file, Bob - an employee of the company SomeEnterprise - creates a file,
skipping to change at page 11, line 8 skipping to change at page 11, line 8
o SomeCSP enforces the changes made by SomeEnterprise o SomeCSP enforces the changes made by SomeEnterprise
o SomeEnterprise requests SomeCSP to transfer Bob's former rights to o SomeEnterprise requests SomeCSP to transfer Bob's former rights to
Bill Bill
Post-conditions: Post-conditions:
o Bob does not have the rights to the file at the cloud provided by o Bob does not have the rights to the file at the cloud provided by
SomeCSP SomeCSP
o Bill has the rights to the file that Bob had had o Bill has the rights to the file that Bob had
Requirements: Requirements:
o SomeEnterprise can securely communicate to SomeCSP all changes o SomeEnterprise can securely communicate to SomeCSP all changes
regarding its employee's identity regarding its employee's identity
o SomeCSP can enforce the requested changes o SomeCSP can enforce the requested changes
o SomeCSP shall be able to log all changes regarding a o SomeCSP shall be able to log all changes regarding a
SomeEnterprise employee's identity SomeEnterprise employee's identity
skipping to change at page 13, line 49 skipping to change at page 13, line 49
(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 the combinations of the applications
running on Private and Public clouds along with the traditional IT running on Private and Public clouds along with the traditional IT
systems. The local YourCoI offices are responsible for establishing systems. The local YourCoI offices are responsible for collecting
personal information and (i.e., setting the user identities and personal information(i.e. user identities and attributes). YourHR
attributes). YourHR services provide means for provisioning and services provide means for provisioning and distributing the employee
distributing the employee identity information across all YourCoI identity information across all YourCoI offices. YourHR also enables
offices. YourHR also enables the individual users (e.g., employees) the individual users (e.g., employees) to manage their personal
to manage their personal information that they are responsible for information that they are responsible for (e.g., update of an address
(e.g., update of an address or a telephone number). or a 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 the large number
of local offices that rely on the diverse IT systems of local offices that rely on the 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
skipping to change at page 14, line 32 skipping to change at page 14, line 32
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 ability to manage the part of personal
information that is in their responsibility information that is in their responsibility
Requirements: Requirements:
o YourHR must ensure that the personal information generated by the o YourHR must ensure that the personal information generated by the
local offices is timely available in a globally-accessible local offices is timely available in a globally-accessible
database database.
o Identity management of the personal data must be secure o Identity management of the personal data must be protected against
unauthorised access and remain confidential to only authorised
parties.
o All operation with identity data must be securely logged o All operation with identity data must be securely logged.
o The logs should be available for auditing o The logs should be available for auditing.
3.5. Transfer of attributes to a relying party web site 3.5. Transfer of attributes to a relying party web site
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 relying party web site B, and the
user authorizes the transfer of data via authorization protocols user authorizes the transfer of data via authorization protocols
(e.g. OAuth, SAML), so selected attributes of the user are (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 web
site B at the time of the user's first visit to that site. site 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 a 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 web site of a relying party B
skipping to change at page 15, line 23 skipping to change at page 15, line 25
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 web site B at the time of the
user's first visit to that site. user's first visit to that site.
Requirements: Requirements:
Relying parties have to be aware of changes to their cached copy, as Relying parties have to be aware of changes to their cached copy, as
these would potentially cause a state change in other relying these would potentially cause a state change in other relying
parties. parties.
A maximum period should be set for the relying party to cache the
information.
3.6. Change notification 3.6. 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 relying party web site B. Relying
party web site B queries directory service A for attributes party web site B queries directory service A for attributes
associated with that user, and related resources. 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 relying party web site B of these changes, as relying party B
might (or might not) have a cache of those attributes, and if the might (or might not) have a cache of those attributes, and if the
relying party B were aware of these changes to their cached copy, relying party B were aware of these changes to their cached copy,
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
skipping to change at page 16, line 28 skipping to change at page 16, line 34
interest. interest.
Requirements: Requirements:
B must be able at an appropriate time to subsequently contact B must be able at an appropriate time to subsequently contact
directory service A and retrieve just the subset of changes of directory service A and retrieve just the subset of changes of
interest to B. interest to B.
4. Security considerations 4. Security considerations
Authorization and authentication must be guaranteed for the SCIM SCIM resources (e.g., Users and Groups) can contain sensitive
operations. information. Therefore, authentication and authorization must be
guaranteed for the SCIM operations.
Also, private information of the SCIM resources must be kept
confidential and protected.
5. IANA considerations 5. IANA considerations
This Internet Draft includes no request to IANA. This Internet Draft includes no request to IANA.
6. Acknowledgements 6. Acknowledgements
Authors would like to thank Ray Counterman, Richard Fiekowsky and Authors would like to thank Ray Counterman, Richard Fiekowsky and
Bert Greevenbosch for their reviews and comments. Bert Greevenbosch for their reviews and comments.
skipping to change at page 17, line 8 skipping to change at page 17, line 15
7. References 7. References
7.1. Normative References 7.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.
7.2. Informative References 7.2. Informative References
[I-D.ietf-scim-api] [I-D.ietf-scim-api]
Grizzle, K., Hunt, P., Ansari, M., Wahlstroem, E., and C. Hunt, P., Grizzle, K., Ansari, M., Wahlstroem, E., and C.
Mortimore, "System for Cross-Domain Identity Mortimore, "System for Cross-Domain Identity
Management:Protocol", draft-ietf-scim-api-03 (work in Management:Protocol", draft-ietf-scim-api-05 (work in
progress), February 2014. progress), May 2014.
[I-D.ietf-scim-core-schema] [I-D.ietf-scim-core-schema]
Grizzle, K., Hunt, P., Wahlstroem, E., and C. Mortimore, Grizzle, K., Hunt, P., Wahlstroem, E., and C. Mortimore,
"System for Cross-Domain Identity Management: Core "System for Cross-Domain Identity Management: Core
Schema", draft-ietf-scim-core-schema-03 (work in Schema", draft-ietf-scim-core-schema-05 (work in
progress), February 2014. progress), May 2014.
Authors' Addresses Authors' Addresses
Phil Hunt Phil Hunt
Oracle Oracle
Email: phil.hunt@oracle.com Email: phil.hunt@oracle.com
Bhumip Khasnabish Bhumip Khasnabish
ZTE USA,Inc. ZTE USA,Inc.
 End of changes. 31 change blocks. 
76 lines changed or deleted 87 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/