Re: [OAUTH-WG] draft-ietf-oauth-jwt-bearer != access tokens (was Re: draft-ietf-oauth-jwt-bearer Shepherd Write-up)

Bill Burke <bburke@redhat.com> Fri, 25 April 2014 19:51 UTC

Return-Path: <bburke@redhat.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B8A31A06AF for <oauth@ietfa.amsl.com>; Fri, 25 Apr 2014 12:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.174
X-Spam-Level:
X-Spam-Status: No, score=-7.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-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 CZB0gQXXo8OM for <oauth@ietfa.amsl.com>; Fri, 25 Apr 2014 12:51:32 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by ietfa.amsl.com (Postfix) with ESMTP id 24D2A1A06EC for <oauth@ietf.org>; Fri, 25 Apr 2014 12:51:32 -0700 (PDT)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s3PJpPQ0022963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 25 Apr 2014 15:51:25 -0400
Received: from [10.10.50.202] (vpn-50-202.rdu2.redhat.com [10.10.50.202]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s3PJpN2f018596; Fri, 25 Apr 2014 15:51:25 -0400
Message-ID: <535ABCBF.3090308@redhat.com>
Date: Fri, 25 Apr 2014 15:51:27 -0400
From: Bill Burke <bburke@redhat.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian Campbell <bcampbell@pingidentity.com>
References: <CA+k3eCTeBZNh8-dhtkjbCJdJ6PfciZQNQOznJj+jdik6Z6Detw@mail.gmail.com>
In-Reply-To: <CA+k3eCTeBZNh8-dhtkjbCJdJ6PfciZQNQOznJj+jdik6Z6Detw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/lfX6QvX_0C2JkHp8bVxvNQO11L0
Cc: oauth <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-jwt-bearer != access tokens (was Re: draft-ietf-oauth-jwt-bearer Shepherd Write-up)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 25 Apr 2014 19:51:34 -0000

Thank you.  Thats what I thought.  Is it just assumed JWT would/might be 
used an access token format for Bearer token auth?  Or is there another 
draft somewhere for that?  Is anybody out there using JWS + JWT as a 
access token format?

On 4/25/2014 2:59 PM, Brian Campbell wrote:
> draft-ietf-oauth-jwt-bearer is only about interactions (client
> authentication and JWT as an authorization grant) with the token
> endpoint and doesn't define JWT style access tokens.
>
>
> On Fri, Apr 25, 2014 at 12:51 PM, Bill Burke <bburke@redhat.com
> <mailto:bburke@redhat.com>> wrote:
>
>     Red Hat Keycloak [1] only supports basic auth for client
>     authentication as suggested in the OAuth 2 spec.  But our access
>     tokens are JWS signed JWTs.
>
>     Does draft-ietf-oauth-jwt-bearer relate to OAuth Bearer token auth
>     [2]?  Or is there another document I should be following?  I'd like
>     to see what other claims are being discussed related to JWT-based
>     access tokens and may have some additional access token claims we've
>     been experimenting with others might be interested in.
>
>     Also, I'm not sure yet if we'll implement
>     draft-ietf-oauth-jwt-bearer to authenticate clients.  A lot of our
>     initial users are more interested in public clients and/or the
>     implicit flow as they are writing a lot of pure javascript apps
>     served up by simple static web servers.
>
>     [1] http://keycloak.org
>     [2] http://tools.ietf.org/html/__rfc6750
>     <http://tools.ietf.org/html/rfc6750>
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com