Re: [OAUTH-WG] Audience parameter in authorization flow
Justin Richer <jricher@mitre.org> Mon, 19 August 2013 14:13 UTC
Return-Path: <jricher@mitre.org>
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 74CA011E8271 for <oauth@ietfa.amsl.com>; Mon, 19 Aug 2013 07:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level:
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tbVyfA6WCZvY for <oauth@ietfa.amsl.com>; Mon, 19 Aug 2013 07:12:56 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2C911E8259 for <oauth@ietf.org>; Mon, 19 Aug 2013 07:12:56 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 93BA61F0CA9; Mon, 19 Aug 2013 10:12:47 -0400 (EDT)
Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 5B4AC1F0CBF; Mon, 19 Aug 2013 10:12:47 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS02.MITRE.ORG (129.83.29.79) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 19 Aug 2013 10:12:47 -0400
Message-ID: <52122704.4030308@mitre.org>
Date: Mon, 19 Aug 2013 10:09:08 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Sergey Beryozkin <sberyozkin@gmail.com>
References: <5210F714.80305@gmail.com>
In-Reply-To: <5210F714.80305@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.83.31.56]
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Audience parameter in authorization flow
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: Mon, 19 Aug 2013 14:13:01 -0000
Both of those make sense to me, and it mimics what "scope" does today. Namely, clients can usually register for a list of scopes that they want access to, then at authorization time they ask for a particular set to be approved by the user. -- Justin On 08/18/2013 12:32 PM, Sergey Beryozkin wrote: > Hi Hannes, All, > > Regarding [1], where would you expect an audience parameter be > provided during the authorization flow ? > > It appears to me it should be provided during the initial redirect > (similarly to a parameter like redirect_uri). > > Also, would it make sense to support pre-registered audience values, > example, a client registers and specifies an audience during the > registration ? > > Thanks, Sergey > > [1] http://tools.ietf.org/html/draft-tschofenig-oauth-audience-00 > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Audience parameter in authorization fl… Sergey Beryozkin
- Re: [OAUTH-WG] Audience parameter in authorizatio… Justin Richer
- Re: [OAUTH-WG] Audience parameter in authorizatio… Sergey Beryozkin
- Re: [OAUTH-WG] Audience parameter in authorizatio… Phil Hunt
- Re: [OAUTH-WG] Audience parameter in authorizatio… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [OAUTH-WG] Audience parameter in authorizatio… Phil Hunt
- Re: [OAUTH-WG] Audience parameter in authorizatio… Hannes Tschofenig
- Re: [OAUTH-WG] Audience parameter in authorizatio… Anthony Nadalin
- Re: [OAUTH-WG] Audience parameter in authorizatio… Phil Hunt
- Re: [OAUTH-WG] Audience parameter in authorizatio… Justin Richer