Re: [OAUTH-WG] Dynamic Client Registration

Hannes Tschofenig <hannes.tschofenig@gmx.net> Sun, 15 April 2012 16:06 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABA921F8744 for <oauth@ietfa.amsl.com>; Sun, 15 Apr 2012 09:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.154
X-Spam-Level:
X-Spam-Status: No, score=-102.154 tagged_above=-999 required=5 tests=[AWL=-0.361, BAYES_00=-2.599, SARE_URI_CONS7=0.306, URI_NOVOWEL=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTojKxZLswHV for <oauth@ietfa.amsl.com>; Sun, 15 Apr 2012 09:06:13 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 1F87921F8743 for <oauth@ietf.org>; Sun, 15 Apr 2012 09:06:05 -0700 (PDT)
Received: (qmail invoked by alias); 15 Apr 2012 16:06:01 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.101]) [88.115.216.191] by mail.gmx.net (mp016) with SMTP; 15 Apr 2012 18:06:01 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+tRENxnE2tjIx6kdlopCsZG5bSsFd/3kX3SXKi/c VvBfeh9EwriTHh
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <1334419265.3552.YahooMailNeo@web31816.mail.mud.yahoo.com>
Date: Sun, 15 Apr 2012 19:06:00 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <997D46FA-F78A-4940-9B56-49C4D2473F01@gmx.net>
References: <5F51A14F-D548-4D29-B20F-5C3DCB3CB705@gmx.net> <3E72A308-75EE-4F5C-96CC-A51F0B81106A@xmlgrrl.com> <1334419265.3552.YahooMailNeo@web31816.mail.mud.yahoo.com>
To: William Mills <wmills@yahoo-inc.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Dynamic Client Registration
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Apr 2012 16:06:14 -0000

Bill,

I actually do not think that the security of either SCIM or this work is particularly challenging. 

For SCIM I assume that there is a close relationship between the SCIM client and a SCIM server (as it is common in an enterprise or single administrative domain scenario). 

For the dynamic registration I assume that there is no relationship between the two in the worst case and therefore this turns into a leap of faith type of provisioning. 

I may be completely wrong here but that's the impression I have at the moment. 

In any case, these questions are something to deal with once we have started the work. At the moment we are still attempting to finalize the re-chartering. 

Ciao
Hannes


On Apr 14, 2012, at 7:01 PM, William Mills wrote:

> Yeah, SCIM as a way to federate and distribute info like this seems sane, with extensions for the data items we need here.  The hard part is still around the security stuff which they have not dealt with yet, and that's going to be a blocker until it's solved.  Authority to update elemnts or namespaces is going to be needed, and that's a hard problem.
> 
> -bill
> 
> From: Eve Maler <eve@xmlgrrl.com>
> To: Hannes Tschofenig <hannes.tschofenig@gmx.net> 
> Cc: "oauth@ietf.org WG" <oauth@ietf.org> 
> Sent: Friday, April 13, 2012 6:29 PM
> Subject: Re: [OAUTH-WG] Dynamic Client Registration
> 
> Hi Hannes-- That's kind of a cool idea. You're right that it's a "client account" of sorts. At least worth exploring, I'd say, unless a SCIM expert pipes up with a reason why not.
> 
>     Eve
> 
> On 13 Apr 2012, at 7:36 AM, Hannes Tschofenig wrote:
> 
> > Hi all, 
> > 
> > at the IETF#83 OAuth working group meeting we had some confusion about the Dynamic Client Registration and the Simple Web Discovery item. I just listened to the audio recording again. 
> > 
> > With the ongoing mailing list discussion regarding WebFinger vs. Simple Web Discovery I hope that folks had a chance to look at the documents again and so the confusion of some got resolved.  
> > 
> > I believe the proposed new charter item is sufficiently clear with regard to the scope of the work. Right? 
> > Here is the item again:
> > "
> > Jul. 2013  Submit 'OAuth Dynamic Client Registration Protocol' to the IESG for consideration as a Proposed Standard
> > 
> > [Starting point for the work will be 
> > http://tools.ietf.org/html/draft-hardjono-oauth-dynreg
> > ] 
> > "
> > 
> > Of course there there is a relationship between Simple Web Discovery (or WebFinger) and the dynamic client registration since the client first needs to discover the client registration endpoint at the authorization server before interacting with it. 
> > 
> > Now, one thing that just came to my mind when looking again at draft-hardjono-oauth-dynreq was the following: Could the Client Registration Request and Response protocol exchange could become a profile of the SCIM protocol? In some sense this exchange is nothing else than provisioning an account at the Authorization Server (along with some meta-data).
> > 
> > Is this too far fetched? 
> > 
> > Ciao
> > Hannes
> > 
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
> 
> 
> Eve Maler                                  http://www.xmlgrrl.com/blog
> +1 425 345 6756                        http://www.twitter.com/xmlgrrl
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
> 
>