Re: [scim] Discovery support for SCIM
Chuck Mortimore <charliemortimore@gmail.com> Mon, 28 September 2015 19:37 UTC
Return-Path: <charliemortimore@gmail.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD0241B2C16 for <scim@ietfa.amsl.com>; Mon, 28 Sep 2015 12:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 fKkrPu6XgAzj for <scim@ietfa.amsl.com>; Mon, 28 Sep 2015 12:37:05 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (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 579641B2C15 for <scim@ietf.org>; Mon, 28 Sep 2015 12:37:05 -0700 (PDT)
Received: by obbbh8 with SMTP id bh8so135817556obb.0 for <scim@ietf.org>; Mon, 28 Sep 2015 12:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UtGYmtswTEkzKFOybhQJOR2VR9/6csYOhoTCyMofT7Q=; b=yyQ4H4HJ/qq428ROSWfxVLmRrt9Ls6UdJAxfHFGHaufoqTwFJtVK3yN+vwfqbGrShZ /SdG4qRiNbnuNaB8CrZA4BB/g86AJGco7thILVEG7dYkWqVLTpii4rnDsg4xyUD7dUid kklUzPENNg23QynpujybmFnbD/Ra4aKSNE8CF4q9x6JXapSKktLHcw9FB9NDDZHb7pF0 2NSearOcRXjHpS8FCeV5KUpfzhwIkurEvba0PSOXEPnLFYJHZRJ88kWwKK/08NbfkqSm AUaVpcC5bnRHAaxKD76WflNa5HGrZ9MHpU2dtgGW5NOEdFbuFwKhzIkQiELEL7/8QydX IrPA==
MIME-Version: 1.0
X-Received: by 10.182.224.163 with SMTP id rd3mr11685007obc.61.1443469024759; Mon, 28 Sep 2015 12:37:04 -0700 (PDT)
Received: by 10.202.174.21 with HTTP; Mon, 28 Sep 2015 12:37:04 -0700 (PDT)
In-Reply-To: <CD73F905-2D21-4A2B-AB6D-BA2C51258F89@oracle.com>
References: <CD73F905-2D21-4A2B-AB6D-BA2C51258F89@oracle.com>
Date: Mon, 28 Sep 2015 12:37:04 -0700
Message-ID: <CAKzGp_6t_YZdzOu3EZkvBf==bM8JcpyCgQpu-urP4-sXe9BE+A@mail.gmail.com>
From: Chuck Mortimore <charliemortimore@gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="089e013a211c7717240520d3d2ae"
Archived-At: <http://mailarchive.ietf.org/arch/msg/scim/pz396Rob2PJEqO5YtkAzp5Ywvj0>
Cc: SCIM WG <scim@ietf.org>
Subject: Re: [scim] Discovery support for SCIM
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 28 Sep 2015 19:37:07 -0000
We're interested, in the service discovery aspect. Less so on the profile discovery / webfinger On Mon, Sep 28, 2015 at 11:58 AM, Phil Hunt <phil.hunt@oracle.com> wrote: > It’s now Monday after completion of the SCIM RFCs and I have already > received a new enhancement request. BTW thanks to everyone in the WG for > all your efforts! > > The request is to define discovery for SCIM. For example using the > Well-known mechanism (RFC5785) and potentially WebFinger (RFC7033). > > For example, a SCIM client may send the following query: > > GET https://www.example.com/.well-known/scim > > For which the server might respond with a URL to the appropriate SCIM > server and path to the server root (e.g. "profile.example.com/scim”). > > In a more complex version with a webfinger (RFC7033) query: > > GET > https://www.example.com/.well-known/webfinger?resource=acct%3Abob%40example.com& > rel=scim-profile > > Which responds: > HTTP/1.1 200 OK > Access-Control-Allow-Origin: * > Content-Type: application/jrd+json > > { > "subject" : "acct:bob@example.com", > "links" : > [ > { > "rel" : “scim-profile", > "href" : "https://www.example.com/sciim/Users/bob-id" > } > ] > } > > > Overall, I see a few different use-cases: > > 1. A SCIM client simply wants to know where the SCIM Profile service is > for a specific domain (e.g. tenacy.example.com). > > 2. A SCIM client might be looking for a user’s profile service. So it > asks example.com where is phil.hunt@acme.com? This would be a WebFinger > style query based on the well-known endpoint. The same WebFinger query > could also return the OIDC endpoints as well as the SCIM endpoints for the > user. This may be useful for cases where service providers have multiple > tenancies and there is a need to have a generic, tenancy neutral lookup > service. > > 3. A SCIM client that has the service endpoint for a SaaS service (e.g. > CRM, HCM, Finance) may be looking for the provisioning endpoint and the > ResourceType and schemas relevant to the application. For example, a > client that wants to provision to a User to a Finance system, wants know > where the Finance app provisioning endpoint is. It could be an Finance > SCIM endpoint or it may a profile service endpoint. > > Questions: > > A. Are there members of the WG interested in this? > > B. From a protocol standpoint, it should not matter whether a client is > talking to SCIM that is deployed in front of a business application (like > CRM, Finance), vs. SCIM as a general User profile service. However, due to > possible difference in the higher-level logic of the client, would it be > important to distinguish between say “scim-provisioning” and “scim-profile” > as distinct types of services? If so, what do we think defines that > difference? > > Thanks, > > Phil > > @independentid > www.independentid.com > phil.hunt@oracle.com > > _______________________________________________ > scim mailing list > scim@ietf.org > https://www.ietf.org/mailman/listinfo/scim >
- [scim] Discovery support for SCIM Phil Hunt
- Re: [scim] Discovery support for SCIM Chuck Mortimore
- Re: [scim] Discovery support for SCIM Phil Hunt
- Re: [scim] Discovery support for SCIM Ian Glazer
- Re: [scim] Discovery support for SCIM Kelly Grizzle