draft-ietf-scim-use-cases-07.txt   draft-ietf-scim-use-cases-08.txt 
SCIM WG K. LI, Ed. SCIM WG K. LI, Ed.
Internet-Draft Alibaba Group Internet-Draft Alibaba Group
Intended status: Informational P. Hunt Intended status: Informational P. Hunt
Expires: November 3, 2015 Oracle Expires: November 8, 2015 Oracle
B. Khasnabish B. Khasnabish
ZTE (TX) Inc. ZTE (TX) Inc.
A. Nadalin A. Nadalin
Microsoft Microsoft
Z. Zeltsan Z. Zeltsan
Individual Individual
May 2, 2015 May 7, 2015
SCIM Definitions, Overview, Concepts and Requirements SCIM Definitions, Overview, Concepts and Requirements
draft-ietf-scim-use-cases-07 draft-ietf-scim-use-cases-08
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 includes user scenarios, use cases,
and requirements. and requirements.
Status of this Memo Status of this Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 November 3, 2015. This Internet-Draft will expire on November 8, 2015.
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
skipping to change at page 2, line 44 skipping to change at page 2, line 44
2.4.3. ECS ->CSP - Delete Identity (Push) . . . . . . . . . . 10 2.4.3. ECS ->CSP - Delete Identity (Push) . . . . . . . . . . 10
2.4.4. ECS ->CSP - SSO Pull . . . . . . . . . . . . . . . . . 10 2.4.4. ECS ->CSP - SSO Pull . . . . . . . . . . . . . . . . . 10
3. SCIM Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 10 3. SCIM Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1. Migration of the identities . . . . . . . . . . . . . . . 10 3.1. Migration of the identities . . . . . . . . . . . . . . . 10
3.2. Single Sign-On (SSO) Service . . . . . . . . . . . . . . . 11 3.2. Single Sign-On (SSO) Service . . . . . . . . . . . . . . . 11
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) . . . . . . . . . . . . . . . . . . . . . . 13
3.4. Transfer of attributes to a relying party web site . . . . 14 3.4. Transfer of attributes to a relying party web site . . . . 14
3.5. Change notification . . . . . . . . . . . . . . . . . . . 15 3.5. Change notification . . . . . . . . . . . . . . . . . . . 15
4. Security considerations . . . . . . . . . . . . . . . . . . . 16 4. Security considerations . . . . . . . . . . . . . . . . . . . 16
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 17
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. Normative References . . . . . . . . . . . . . . . . . . . 17 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 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
skipping to change at page 16, line 42 skipping to change at page 16, line 42
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 PII offshore between CSPs. Regulatory requirements shall be
met when migrating identity information between jurisdictional met when migrating identity information between jurisdictional
regions (countries, state-by-state for regulations on privacy. regions (countries, state-by-state for regulations on privacy.
Additionally, privacy sensitive data elements may be omitted or
obscured in SCIM transactions or stored records to protect these data
elements for a user. For instance a role based identifier might be
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 SCIM
protocol [I-D.ietf-scim-api] and section 9 of SCIM schema protocol [I-D.ietf-scim-api] and section 9 of SCIM schema
[I-D.ietf-scim-core-schema]. [I-D.ietf-scim-core-schema].
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
 End of changes. 6 change blocks. 
5 lines changed or deleted 10 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/