IETF Logo Mail Archive

Re: [OAUTH-WG] RFC 7662 OAuth 2.0 Token Introspection: token_type

Vladimir Dzhuvinov <vladimir@connect2id.com> Tue, 24 November 2015 14:20 UTC

Return-Path: <vladimir@connect2id.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 BADDE1A7001 for <oauth@ietfa.amsl.com>; Tue, 24 Nov 2015 06:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 i-eQrWrnsKCA for <oauth@ietfa.amsl.com>; Tue, 24 Nov 2015 06:20:33 -0800 (PST)
Received: from p3plsmtpa09-01.prod.phx3.secureserver.net (p3plsmtpa09-01.prod.phx3.secureserver.net [173.201.193.230]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DA371A6FF8 for <oauth@ietf.org>; Tue, 24 Nov 2015 06:20:33 -0800 (PST)
Received: from [192.168.0.106] ([77.77.164.50]) by p3plsmtpa09-01.prod.phx3.secureserver.net with id lSLX1r00D15ZTut01SLYkU; Tue, 24 Nov 2015 07:20:33 -0700
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "oauth@ietf.org" <oauth@ietf.org>
References: <564B045C.50301@connect2id.com> <564B0C9A.5030809@gmx.net>
From: Vladimir Dzhuvinov <vladimir@connect2id.com>
Organization: Connect2id Ltd.
Message-ID: <5654722E.3030708@connect2id.com>
Date: Tue, 24 Nov 2015 16:20:30 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <564B0C9A.5030809@gmx.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms010907050505010202020004"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/rro4mdJIMC5xIPsdSKoVryE2rPw>
Subject: Re: [OAUTH-WG] RFC 7662 OAuth 2.0 Token Introspection: token_type
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 24 Nov 2015 14:20:38 -0000

Thank you Hannes,

If the inspected token is a refresh token (which is permitted by the
spec), what should the token_type response say?

Vladimir

On 17.11.2015 13:16, Hannes Tschofenig wrote:
> Hi Vladimir, > > it is 'Bearer'. > > Section 5.1 in RFC 6749 defines the token_type
concept and RFC 6750 > registers the 'Bearer' token value (since it
defines the bearer token > concept). > > We currently have work going on
with the PoP token work to also extend > the concept further. > > Ciao >
Hannes > > > On 11/17/2015 11:41 AM, Vladimir Dzhuvinov wrote: >> The
"token_type" parameter in introspection responses - is that supposed >>
to be "access_token" / "refresh_token", or the type of the access token,
>> e.g. "Bearer"? >> >> https://tools.ietf.org/html/rfc7662#section-2.2
>> >> Section 5.1 in RFC 6749 that is referred to points to section 7.1
which >> seems to imply the latter? >> >>
http://tools.ietf.org/html/rfc6749#section-7.1 >> >> Thanks, >> >>
Vladimir >> >> >> >> _______________________________________________ >>
OAuth mailing list >> OAuth@ietf.org >>
https://www.ietf.org/mailman/listinfo/oauth >> >

-- 
Vladimir Dzhuvinov :: vladimir@connect2id.com

v2.23.0 | Report a Bug | By Email