Re: [scim] Is ServiceProviderConfig Required?

Phillip Hunt <phil.hunt@independentid.com> Wed, 13 October 2021 15:58 UTC

Return-Path: <phil.hunt@independentid.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE4CC3A0BBC for <scim@ietfa.amsl.com>; Wed, 13 Oct 2021 08:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQY2kpcFe2pt for <scim@ietfa.amsl.com>; Wed, 13 Oct 2021 08:57:56 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6D773A0BB9 for <scim@ietf.org>; Wed, 13 Oct 2021 08:57:56 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id m14so2847851pfc.9 for <scim@ietf.org>; Wed, 13 Oct 2021 08:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=Inx05PdggfqPUAYHe0VW0Zs8cuul0Trkn3JN9CMN7QE=; b=OY1sK/QXHkMekM6muxGpZqwZwj3XXiL3DQMfi7WzLCVET2ohsp/AaDagQ9onOgugPt chRVWfSmh682N5dyFlcIQ5hqutbEMa5qqGlhjga94fETHLwAsKGqJSmj3DVq41cBeI9K FRPbQ+JmtR1fkjv35doQUo4kbNeLp3+XeQu6tKSsDgrbATZpVo1HUnjep+5dL/GM7smy q94wC3/cvfiIwLPzY7tNfccMN+l0VoQUQOpGcsDcOg4YlihAGkIaBFisFhb0ZXKYvDFJ JwUwLtvHjUvDGZtrqGvJHWQjWSU/Mmw02IPxsUIXlQrtL+5O8BMZtCMFf6VHzeBhOOAl SYQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=Inx05PdggfqPUAYHe0VW0Zs8cuul0Trkn3JN9CMN7QE=; b=ai0uQXtypTXSIcIIbCnFqoFLQ79w2aGNJsG8IPHLz/MzF4fAxShakJpwuurprKNmAe R+uyY6v6b416zmIVgiwgDGwFqdSkmNR2EOEd9Ov27Rdllxi97T9mABERX77TuvR/3fwf y6ZjtxIbKLsJMhx1Dcev05TvwnX4aHYbN4tKIV8HA19TE66m2TLQh+a3wScnHG/iase2 KzilPVTtNxIbJD9m5YYxgsxsRW4lwe3bz/LVrPs5cT4C62Mniq7chrpYfGhVzKWcW9Uv D8Qdq9tj4OfkhW92K2KObo9dwmRmKDg+liI5L9kwnZLwiNly8dDn0jD4nLaDpqKfQvkv 8YQQ==
X-Gm-Message-State: AOAM5329Qvg0h4q2LqT24dJ3oppvDVBaNTkYzMcFzPMbhgi4i6tvTZ40 RojX08exBg7lw0za1DVOmmMKfv/ESx9/5Q==
X-Google-Smtp-Source: ABdhPJw+9oPIPT7pqecN0POnAj0NHy9/DjV7KbJcC1H6z+1uDpsOm5uM4INOs8Z9spKkIi4o8QH+8g==
X-Received: by 2002:a63:6c02:: with SMTP id h2mr13887237pgc.173.1634140675748; Wed, 13 Oct 2021 08:57:55 -0700 (PDT)
Received: from smtpclient.apple (node-1w7jr9qjhqzxo0ctyt6lkjl18.ipv6.telus.net. [2001:569:7316:ae00:4d88:4b67:7bdb:993c]) by smtp.gmail.com with ESMTPSA id oo9sm11298pjb.53.2021.10.13.08.57.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Oct 2021 08:57:55 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Phillip Hunt <phil.hunt@independentid.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 13 Oct 2021 08:57:54 -0700
Message-Id: <E45706C7-043E-41E8-A638-58AA452D11E4@independentid.com>
References: <9f90574b-aa33-4f06-209b-6281a3ab6600@pdmconsulting.net>
Cc: SCIM WG <scim@ietf.org>
In-Reply-To: <9f90574b-aa33-4f06-209b-6281a3ab6600@pdmconsulting.net>
To: Danny Mayer <mayer@pdmconsulting.net>
X-Mailer: iPhone Mail (19A348)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/ZuP5nSm4HJFOlwTa_262PTbtKCA>
Subject: Re: [scim] Is ServiceProviderConfig Required?
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2021 15:58:02 -0000

Inline

Phil

> On Oct 13, 2021, at 8:24 AM, Danny Mayer <mayer@pdmconsulting.net> wrote:
> 
> I've been looking at some SCIM servers and it seems that some do not provide the ServiceProviderConfig endpoint and at least one Commercial SCIM Client didn't request the endpoint when I was testing it last year. Is it a requirement to provide this endpoint and is the client required to read it and obey the rules laid out in the returned information? Are clients using it?

ServiceProviderConfig is the standard way to do functionality, schema and resource type discovery. 

As a discovery feature it is technically optional. It does seem silly not to implement it since for many its fairly simple to implement. 

I have heard of many smarter clients that use it. I2scim.io client does discovery to defines its own schema to match. 
> 
> I'm also not sure about the /Me endpoint. That requires that the SCIM server retain state. That should be the SCIM client's responsibility.

Not sure what you mean here. The server just uses the authorization header to locate what /Me refers to.  Eg matching username or sub claim. 

> 
> Danny
> 
> 
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim