Re: [OAUTH-WG] OAuth Discovery Requirements

David Recordon <recordond@gmail.com> Mon, 02 August 2010 21:35 UTC

Return-Path: <recordond@gmail.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82C653A69BB for <oauth@core3.amsl.com>; Mon, 2 Aug 2010 14:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.378
X-Spam-Level:
X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzkidYXNfN+b for <oauth@core3.amsl.com>; Mon, 2 Aug 2010 14:35:23 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id EC12E3A6877 for <oauth@ietf.org>; Mon, 2 Aug 2010 14:35:22 -0700 (PDT)
Received: by iwn3 with SMTP id 3so422909iwn.31 for <oauth@ietf.org>; Mon, 02 Aug 2010 14:35:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=h9P+ccGTNjfLcrrvoxpE3Pg8tUTy/IzmKzXWmTgphXc=; b=j3tw9wk+ODsVRGAfHCCqnrz84TgCuUPpCEex3fyrm3zetSO4EZj+/JlSs6HazzDNGI 7KhgBoTGB735+278lpIqKjp72H5oDBBALB2QAhuOubvkuXkSgKeXLlzDEO5NWxEDPAW8 sBnwgH1CTyN942KtR9Ejws1VLmWphJycktsbE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ktYvElrLs3jq8wEg0gG1A3wKseVQaH2RZc7kmJIeACaSgSkc0FSSpxHrctut02ZqQu Lzw79jOtttun5JwFRo80vrEaiTOHwQf1RtAxjJGTpSR8y9FHuJbcbDytBMQoJ7IKRsEa lqOCGgl5KUWmPswO6fWVIUZoPwJ6KQp3+OEsw=
MIME-Version: 1.0
Received: by 10.231.190.10 with SMTP id dg10mr7584884ibb.46.1280784949901; Mon, 02 Aug 2010 14:35:49 -0700 (PDT)
Received: by 10.231.174.2 with HTTP; Mon, 2 Aug 2010 14:35:49 -0700 (PDT)
In-Reply-To: <FFDFD7371D517847AD71FBB08F9A31562E248B4D@SP2-EX07VS06.ds.corp.yahoo.com>
References: <4C572883.7020302@lodderstedt.net> <AANLkTi=he7cZGZ01R1M-y0r-461kRZ+KspYdAnp78mVH@mail.gmail.com> <FFDFD7371D517847AD71FBB08F9A31562E248B4D@SP2-EX07VS06.ds.corp.yahoo.com>
Date: Mon, 02 Aug 2010 14:35:49 -0700
Message-ID: <AANLkTimOfTNCF2E7hhcb9kjKiEhv3t_Bbcwgd69-J8Ox@mail.gmail.com>
From: David Recordon <recordond@gmail.com>
To: William Mills <wmills@yahoo-inc.com>
Content-Type: multipart/alternative; boundary="0016367b6e8cf8f857048cddfb00"
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth Discovery Requirements
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 02 Aug 2010 21:35:24 -0000

Yes, all of these all seem like the right set of use cases. I'm not sure if
I'll have much time to devote to them over the next few months though.

--David


On Mon, Aug 2, 2010 at 2:14 PM, William Mills <wmills@yahoo-inc.com> wrote:

> Client discovery can be useful for presenting a nicer user experience in
> token management for example, displaying a favicon for example to help
> identify the tokens listed for revocation.
>
> > -----Original Message-----
> > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org]
> > On Behalf Of Marius Scurtescu
> > Sent: Monday, August 02, 2010 1:47 PM
> > To: Torsten Lodderstedt
> > Cc: OAuth WG (oauth@ietf.org)
> > Subject: Re: [OAUTH-WG] OAuth Discovery Requirements
> >
> > Does anyone see value in client discovery?
> >
> > A client starts a transaction with an authz server without
> > doing any registration beforehand. Based on the client id
> > (which can be a URL or a domain name) the authz server can
> > discover information about the client, information that
> > normally is provided during registration:
> > client name, description, logo, redirect URI.
> >
> > The client can self assert all this information as well, but
> > with discovery the authz server at least is confident the
> > client controls the domain where the redirect URI is.
> >
> > There is no client secret issued in this case, that could be
> > a separate call, but the discovery info could include a
> > public key to be used with signatures.
> >
> > Marius
> >
> >
> >
> > On Mon, Aug 2, 2010 at 1:20 PM, Torsten Lodderstedt
> > <torsten@lodderstedt.net> wrote:
> > > In the WG meeting at Maastricht, I have been asked to write down my
> > > requirements regarding Discovery. And here they are:
> > >
> > > Assumptions: Discovery allows a compliant client to automatically
> > > obtain all deployment specific data required to securely access a
> > > particular resource servers as well as its respective authorization
> > > server for the purpose of obtaining access tokens.
> > >
> > > Starting point of the discovery process is a resource URL. This URL
> > > can be hard-coded into the client, bundled with the applications
> > > resources or manually configured by the end-user at runtime.
> > >
> > > 1) Client -> Resource
> > > The client uses the resource URL to obtain resource-specific data,
> > > such as
> > > a) one URI refering to its authorization server
> > > b) a definition of all scopes of the resource
> > > c) additional data, e.g. supported signature methods and algorithms
> > >
> > > I do not make any assumption about how many requests are
> > processed in
> > > order to gather this information and whether there will be
> > any levels
> > > of indirections (e.g. from resource to resource server).
> > >
> > > 2) Client -> Authz Server
> > > The authz server URI obtained in step 1 is used to gather the
> > > following data from the authz server:
> > > a) endpoint URLs (end-user authorization, tokens, ...)
> > > b) information about the server's capabilities, e.g. the supported
> > > response (end-user authorization endpoint) and grant types (tokens
> > > endpoint)
> > >
> > > The client stores the authz server's discovery URL along with the
> > > token(s) it obtains for further use.
> > >
> > > And that's it from my point of view. I would very much
> > appreciate if
> > > we could have a discussion towards a consensus about
> > discovery requirements.
> > >
> > > regards,
> > > Torsten.
> > >
> > >
> > >
> > > _______________________________________________
> > > OAuth mailing list
> > > OAuth@ietf.org
> > > https://www.ietf.org/mailman/listinfo/oauth
> > >
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
> >
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>