SCIM Profile for Provisioning Users Into Relying Party Applications
draft-wahl-scim-profile-00

Document Type Active Internet-Draft (individual)
Last updated 2019-06-21
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                             M. Wahl, Ed.
Internet-Draft                                     Microsoft Corporation
Intended status: Standards Track                           June 21, 2019
Expires: December 23, 2019

  SCIM Profile for Provisioning Users Into Relying Party Applications
                       draft-wahl-scim-profile-00

Abstract

   This document specifies a profile of the System for Cross-Domain
   Identity Management Protocol (SCIM).  This profile defines how an
   identity provider, acting as a SCIM client, can notify a relying
   party application of changes to user accounts.

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 https://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 December 23, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Wahl                    Expires December 23, 2019               [Page 1]
Internet-Draft     SCIM Profile for Relying Party Apps         June 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  General Considerations  . . . . . . . . . . . . . . . . . . .   4
     2.1.  Endpoints and Payload . . . . . . . . . . . . . . . . . .   4
     2.2.  Authentication and Authorization  . . . . . . . . . . . .   5
     2.3.  SCIM Servers With Multiple Identity Providers and
           Multiple tenants  . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Case Sensitivity in Payloads  . . . . . . . . . . . . . .   6
     2.5.  Overlapping and Throttling Requests . . . . . . . . . . .   6
     2.6.  Bulk Operations and Service Provider Configuration  . . .   7
     2.7.  Error Results . . . . . . . . . . . . . . . . . . . . . .   7
     2.8.  Non-Requirements  . . . . . . . . . . . . . . . . . . . .   7
   3.  Minimum Schema and Schema Discovery . . . . . . . . . . . . .   7
     3.1.  Additional Considerations for the ID Attribute  . . . . .   9
     3.2.  Additional Considerations ExternalId Attribute  . . . . .   9
     3.3.  Resources for Schema Discovery  . . . . . . . . . . . . .  10
   4.  Operations on Users . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  When a User Account is added in the Identity Provider . .  12
       4.1.1.  Optionally locating a User by ExternalId  . . . . . .  12
       4.1.2.  Creating a User with POST . . . . . . . . . . . . . .  13
     4.2.  When a User Account's Attributes Change . . . . . . . . .  14
       4.2.1.  Retrieving a User by ID . . . . . . . . . . . . . . .  15
       4.2.2.  Modifying a User with PATCH . . . . . . . . . . . . .  16
       4.2.3.  Indicating User Sign In Blocked . . . . . . . . . . .  18
     4.3.  When the User's Account is to be Removed  . . . . . . . .  19
       4.3.1.  Removing a User with DELETE . . . . . . . . . . . . .  19
     4.4.  User Account Retrieval from the Relying Party . . . . . .  20
       4.4.1.  Retrieving Multiple Users in a Single Request . . . .  20
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  21
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  22
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   Relying party applications implement single-sign on protocols, such
   as SAML or OpenID Connect, for user authentication from an identity
   provider, and often store one or more attributes about each of user
   identities from those identity providers.  The term relying party is
Show full document text