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

Sergey Beryozkin <sberyozkin@gmail.com> Fri, 15 January 2016 13:47 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 0B1831B2D14 for <oauth@ietfa.amsl.com>; Fri, 15 Jan 2016 05:47:54 -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 lIpkGLbUYUr1 for <oauth@ietfa.amsl.com>; Fri, 15 Jan 2016 05:47:52 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 4562B1B2D13 for <oauth@ietf.org>; Fri, 15 Jan 2016 05:47:52 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id f206so21014653wmf.0 for <oauth@ietf.org>; Fri, 15 Jan 2016 05:47:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=hYlBGzXyEdtWGkq/ecGLI5ZbfIwXIKM1YkysVfncrKo=; b=0cNFo36jpY4/0MWBrvrtsV9nmZH0DlVOHEPcjVVZ47l6aCXN5EsRwc69nb9SkFPKjI OAcSdZM2W48grDYFQWjplgEyAbZXZYl4gEDTrtQ8txILIp0K7akP44/jRlvg0ylQRLVh sMd1cPLrMC1/wd2CKZPTJ86erAF4ucUtkVfsqgRsUkv2eDQYCwxw1qPHfQBRG1bKrTag 6t8xOCPrTZKf0woXyke2c7RqNpX07I3+SJOZ4cHC2EwPbisCtwGJx7nvD7A//CElkEst u6yQfCx2l6/93QeKG/AUIow98HHAn4IB0aJzTvM/0Y+vbFaddRRpY1LW673spxYra/UI 6eqA==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=hYlBGzXyEdtWGkq/ecGLI5ZbfIwXIKM1YkysVfncrKo=; b=l1HbQgXg2ZZJ07hvpXaLaV+2tV1aFxixwP0X2joj+z20GZUr07+hI5/S0KQeTga0D1 RSwzInfLsF+XrGgLoY5l6LSshwpZfoqsT5L4yheDd/FsAJxLnGYV6jPMwMQQjibXwtQZ eVoIqRyNb7vfIlFV5K3by3OLgkeHTtvuMpPWpIEETb37H6/AcQJCpiW3JoYqQEf/fbmg hXv/vNUEna5N+KYotdvtWQWgxNyHQ1rZ1y3BZedMQrFwqPVCtQioRJ4IeKpfNpJy1syp HOCbcYjUTdncj2iOnB26YlNCxygVX2LCk5Y+n1uheTyvWInbGNXgozdxHV4VcXhcllNt S7lg==
X-Gm-Message-State: AG10YOSocv4G0F6izThJm2qKOqETG91yAiILYMka/rmMA5cyxXHe1M1hRA7rnyC4u5BLgQ==
X-Received: by 10.28.146.8 with SMTP id u8mr3362959wmd.72.1452865670800; Fri, 15 Jan 2016 05:47:50 -0800 (PST)
Received: from [10.36.226.98] ([80.169.137.63]) by smtp.googlemail.com with ESMTPSA id v82sm2629112wmv.12.2016.01.15.05.47.49 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jan 2016 05:47:49 -0800 (PST)
To: John Bradley <ve7jtb@ve7jtb.com>
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> <5698CB3D.1030306@gmail.com> <69B0E23E-818A-4FE4-81A0-A8106EB6C312@ve7jtb.com>
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <5698F885.3030009@gmail.com>
Date: Fri, 15 Jan 2016 13:47:49 +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: <69B0E23E-818A-4FE4-81A0-A8106EB6C312@ve7jtb.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/4UgO9QD0YoA3tPi-7R059Ch4db4>
Cc: oauth@ietf.org
Subject: Re: [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 13:47:54 -0000

Hi John

Thanks, looks like it was a last minute change because Introduction does 
not explain why would clients want to use the introspection endpoint to 
effectively 'unwrap' the opaque token representations.

I have another question. How to report the expiry time in cases when the 
tokens do not expire ? I'm aware of some deployments where access tokens 
are only manually deleted and otherwise would not expire.

Perhaps not reporting the expiry time is equivalent to the token never 
expiring ? Or may be reporting 0 or -1 works ?

Thanks, Sergey
On 15/01/16 13:32, John Bradley wrote:
> Some people wanted the client to be able to use introspection.
>
> The ability to pass a refresh token is a legacy of that.    A RS would never have a refresh token unless it is acting as a client.  That is correct.
>
> John B.
>
>> On Jan 15, 2016, at 5:34 AM, Sergey Beryozkin <sberyozkin@gmail.com>; wrote:
>>
>> 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
>>
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>