Re: [OAUTH-WG] audience (was draft-ietf-oauth-jwt-bearer-06)

Chuck Mortimore <cmortimore@salesforce.com> Wed, 06 November 2013 05:21 UTC

Return-Path: <cmortimore@salesforce.com>
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 117DA21E80AE for <oauth@ietfa.amsl.com>; Tue, 5 Nov 2013 21:21:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 jbugthYqQkA0 for <oauth@ietfa.amsl.com>; Tue, 5 Nov 2013 21:21:17 -0800 (PST)
Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) by ietfa.amsl.com (Postfix) with ESMTP id C463121E80B5 for <oauth@ietf.org>; Tue, 5 Nov 2013 21:21:17 -0800 (PST)
Received: by mail-oa0-f47.google.com with SMTP id k1so1656485oag.20 for <oauth@ietf.org>; Tue, 05 Nov 2013 21:21:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=oiOcgGuyGVqJN0Q5/AVJmyzbk8I2bORh2pPwCE/LRAk=; b=dgLfq7jZb/MbZrwf6sLGVpqVxQdNVg5WLp5vDmb455Sam7ictwzLQ1BrCMro1iNF7i h1OmZO/0v2tvlD/6n+ff8VU9SOGCoxs5Gc5grDX2Qbb6bRXA5tf5rtVTy/j61jxSzxzm CnAQkaxmAdeo/sUkCCffJZQuKMnQpj6MOYf3VFhst6S/Erkscx3VFvOkUat4B64UrSBR toNQZ/rMi4R36BwtHEljL+Q/REJHc9oCp8QXLXNz9ys5VBjR4rdMlKOy0PLlnNzFGJeh PNzPdAdKxro4n75Sd8dq14//uJhZAXEiJt84wwAnSbR49d7uh4jUSxqNNfPHKt44Gkcx IBTg==
X-Gm-Message-State: ALoCoQmzoPM1C6qYx9nf/aWbf29/e1dm25f/W+seka/X0t3UTkfGKfOoxClwwwkqPwBTf9miXP2L
MIME-Version: 1.0
X-Received: by 10.182.40.201 with SMTP id z9mr1112269obk.45.1383715277283; Tue, 05 Nov 2013 21:21:17 -0800 (PST)
Received: by 10.76.24.162 with HTTP; Tue, 5 Nov 2013 21:21:17 -0800 (PST)
In-Reply-To: <CA+k3eCQFOsMbV=8vxawtg1ts7jPngUwab8RY8ah+2A8Bh1ZjiA@mail.gmail.com>
References: <CA+k3eCQFOsMbV=8vxawtg1ts7jPngUwab8RY8ah+2A8Bh1ZjiA@mail.gmail.com>
Date: Tue, 5 Nov 2013 21:21:17 -0800
Message-ID: <CA+wnMn-=zu8SV6YRETp-J3AVC_YZ-SaP7UV4GYKckK-SKgZocQ@mail.gmail.com>
From: Chuck Mortimore <cmortimore@salesforce.com>
To: Brian Campbell <bcampbell@pingidentity.com>
Content-Type: multipart/alternative; boundary=001a11c33b0292b6cc04ea7b51a3
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] audience (was draft-ietf-oauth-jwt-bearer-06)
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: Wed, 06 Nov 2013 05:21:22 -0000

On Mon, Nov 4, 2013 at 10:45 AM, Brian Campbell
<bcampbell@pingidentity.com>wrote;wrote:

> On Fri, Nov 1, 2013 at 1:52 PM, Hannes Tschofenig
> <hannes.tschofenig@gmx.net> wrote:
> > You write:
> >
> > "
> >  3.   The JWT MUST contain an "aud" (audience) claim containing a
> >         value that identifies the authorization server as an intended
> >         audience.  The token endpoint URL of the authorization server
> >         MAY be used as a value for an "aud" element to identify the
> >         authorization server as an intended audience of the JWT.  JWTs
> >         that do not identify the authorization server as an intended
> >         audience MUST be rejected....
> > "
> >
> > If the endpoint URL of the AS is not used then what else? Wouldn't it be
> > useful to say "The token endpoint URL of the authorization server
> >         MUST be used as a value for an "aud" element to identify the
> >         authorization server as an intended audience of the JWT."?
>
> This and the other assertion documents offer the token endpoint URL as
> one way to identify the AS for deployments which lack some other means
> of doing so. However, these assertion profiles are little slices of
> functionality that augment existing deployments of OAuth, often in
> conjunction with other 'federated' technologies for which there will
> be an existing and agreed upon identifier that the issuer is known by.
> This is not just academic - it's how these systems and deployment
> already work. It's inappropriate and unrealistic for this document (or
> the other assertion docs) to preclude common and useful deployment
> practices.
>

Agreed.


>
> > Then, I have a suggestion for re-phrasing this sentence from :
> > "
> >         Audience values SHOULD be compared
> >         using the Simple String Comparison method defined in Section
> >         6.2.1 of RFC 3986 [RFC3986], unless otherwise specified by the
> >         application.
> > "
> > to:
> >
> > "
> > In the absence of an application profile standard specifying
> > otherwise, a compliant JWT Bearer application MUST compare the audience
> > values using the Simple String Comparison method defined in Section
> >         6.2.1 of RFC 3986 [RFC3986].
> > "
>
> I think I'm okay with that re-phrasing. Do others (my co-authors
> especially) agree? Or object?
>

I'm good with it.

-cmort



>
> >
> > The same can actually be applied to the issuer claim as well.
>
> As I said in the previous mail about issuer, I'd like to get rid of
> the comparison text. However, if such text stays, I'll work to make it
> consistent throughout.
>
> > Given that the JWT had been updated to align it with the JOSE work I
> suspect
> > that this document also requires an update.
>
> You may well be correct. But despite following the JOSE and JWT work,
> I'm not sure I know what update(s) would be required. Can you
> elaborate?
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>