[OAUTH-WG] Question about RFC 7622 (Token Introspection)

Sergey Beryozkin <sberyozkin@gmail.com> Fri, 15 January 2016 10:34 UTC

Return-Path: <sberyozkin@gmail.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 401571A913E for <oauth@ietfa.amsl.com>; Fri, 15 Jan 2016 02:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 0i7qWBPGpgYe for <oauth@ietfa.amsl.com>; Fri, 15 Jan 2016 02:34:51 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1911A913A for <oauth@ietf.org>; Fri, 15 Jan 2016 02:34:50 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id f206so14724245wmf.0 for <oauth@ietf.org>; Fri, 15 Jan 2016 02:34:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=Jqvxc7atuogCe6lu1K7BOd3IbnbNJ8NjhwU6QPsmFO0=; b=m++duywAxcE8Jy05fAkzCdy9CKx+qPHUB6HDdOCwdkAugEUOdqI/tYXF2Ji4vMEBtT IwMIEHPO0CAqHHzq12JxNycKvtex6N4MTX/xKWkvfWrT6lgset4AoLWhWu7uqJ4IeTyR 2dHDCagsb4SOcuPbPGE9HeTdgVbbm9k+QVz2kyOJ2fuca2E9i4WD7VQunpOHxRDQO82P wcCFJgmp7UK7QVhG0puPxhj5ySJnyaz0lfEeZVms8Swpi2vMzcdccDdmJmqOC623ggV2 3D8QjZUen3G7SzztcmSAoQXe6Upx6o4qCg0XumUA4A6CsWaGSJ+5giALBo6QLXEtmjge 5FyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Jqvxc7atuogCe6lu1K7BOd3IbnbNJ8NjhwU6QPsmFO0=; b=ETWUqYFvG1arfm+9kkqZMZihT89dWTr/+KRCc/hnfjdX0uWbpgMH1CnODZ0Jbu7F9o 6iHJkM4+LK3aSLGZ/I6ZWi3yzl5eMPvaVRIROh4eBex8rbD9q+TTEFHhp6wSBQx6i1S2 Rwze0e+KWDXliTcHSOEOb6vJ3dizaY+z5RqJbBKWgUw9VO306i3wK9xent7ccXdvir12 rTQH8VOcONuvkGghVt4wv3SeoXYatlG/TS79TGhITqlw/dOfKraP6ZZYYbeKI2LdmXJN cOg4koCrOvohW6BfNOXXKAAJvu7/lTdkaVzvDPmaaYbHUe6/+ITzcJLlJm4ZpzBaPVb+ z6TA==
X-Gm-Message-State: AG10YOS1J+Ekxy6+c/f5Hc8pA0ul5TS/ceGXpThGlrxEJD7xpzf/0JkjgXqYXLS6caEOXA==
X-Received: by 10.28.146.8 with SMTP id u8mr2430697wmd.72.1452854089507; Fri, 15 Jan 2016 02:34:49 -0800 (PST)
Received: from [10.36.226.98] ([80.169.137.63]) by smtp.googlemail.com with ESMTPSA id k130sm1954818wmg.6.2016.01.15.02.34.48 for <oauth@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jan 2016 02:34:48 -0800 (PST)
To: oauth@ietf.org
References: <CA+k3eCSpWFwyvk=XHP4b_zxzu-zrMYsS-axF6csO90-ahmkueQ@mail.gmail.com> <BY2PR03MB4423033D5604E9E36B20C23F5CA0@BY2PR03MB442.namprd03.prod.outlook.com> <5CA9073D-BBF7-48BD-BEC5-1F626E8C3818@mit.edu> <8EB68572-DA59-482D-A660-FA6D9848AAD2@oracle.com> <ade5692aa1afa2d9d79b8ac7a55bf150@lodderstedt.net>
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <5698CB3D.1030306@gmail.com>
Date: Fri, 15 Jan 2016 10:34:37 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <ade5692aa1afa2d9d79b8ac7a55bf150@lodderstedt.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/ZD_x_6p0h1XCspf_CXD8o9a3l0g>
Subject: [OAUTH-WG] Question about RFC 7622 (Token Introspection)
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: Fri, 15 Jan 2016 10:34:52 -0000

Hi All,

I'm reviewing RFC 7622 as we are going ahead with implementing it.
I have a question:

1. Token Hint in the introspection request.
The spec mentions 'refresh_token' as one of the possible values. But a 
protected resource does not see a refresh token (ever ?), it is Access 
Token service which does.
When would a protected resource use a 'refresh_token' hint when 
requesting an introspection response ?

Thanks, Sergey