Re: [OAUTH-WG] Question about RFC 7622 (Token Introspection)
Sergey Beryozkin <sberyozkin@gmail.com> Fri, 15 January 2016 14:15 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 00B101B2D67
for <oauth@ietfa.amsl.com>; Fri, 15 Jan 2016 06:15:06 -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 KEW183W3Vfex for <oauth@ietfa.amsl.com>;
Fri, 15 Jan 2016 06:15:04 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com
[IPv6:2a00:1450:400c:c09::22f])
(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 6C1991B2D60
for <oauth@ietf.org>; Fri, 15 Jan 2016 06:15:04 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id f206so26654666wmf.0
for <oauth@ietf.org>; Fri, 15 Jan 2016 06:15:04 -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=yj7q7vspNN9bn591zrbypIsNOsAt0eY4AilwKVxdT2g=;
b=afYtEgO0qi/uTe1xjiF1jP69oMN8A2zaMRtpM9ilu2ZqEMbnpa+MJK0WdIRuhN28bm
/hujJqCe2EK6n80M+bwKTWoJ7O75MvgWMYP1eYGEC1o1xnU/4ILMHfbkBaY6+02hfE2v
G0Z8+T2OG6/PmH5dIZY0F8pJDLT4ckOMACnUeAik42mU+m+uZ4U4Z1a2TLCoQOvQ1ja0
ygQvD1VUyGnFpToxmKkKr/uUFYJf0fdvF6jtbCFeU+a5IDOvRYZ+N8xAApkAYr+5RIBt
aHWMZr59eUiSiDcEg2WQfJvDao9tF1Cu2YPc1nbVXL4zC2T9QfQf9PHtPl1hFfmcAe9s
F0kQ==
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=yj7q7vspNN9bn591zrbypIsNOsAt0eY4AilwKVxdT2g=;
b=GJCiy5CxoHZW4PeMxTOfh7BirT0dSIm/2payD586rxN1Lz/REShJ+y4UldRF6nGyKk
oNxC7uonapxTUAY310Gy6KDkaENllQmOSnpjgXGLyblh/ByaJZ7XObE2t9Zs/PEHFeww
ooHgUtlViB152ESSnKO2oIURAebVvDD2Gnya7s4Tuxcd2Dclt0h4dW/iN9+Yvsj5jkvK
b/SbCGh9QquqwxL56GCbxHrvSNSWRJA/aIH2JNO/lgFlGKx1EP4nnWVDhzZ+let9lSFK
1oKNBBSHRtgPU+6aAIDQDQycTjo+Igd/HsUVwC7T7qXbtH9Eq1qgtQves7MszRuPffE2
EWoA==
X-Gm-Message-State: AG10YORpqjnWbJvs/lJZ+HiE2mO5P2ueznp8jl/4jNGmiIgig05hGRLE17nR4pSY+XRRAA==
X-Received: by 10.28.113.220 with SMTP id d89mr3834553wmi.56.1452867303084;
Fri, 15 Jan 2016 06:15:03 -0800 (PST)
Received: from [10.36.226.98] ([80.169.137.63])
by smtp.googlemail.com with ESMTPSA id 75sm2712404wmo.22.2016.01.15.06.15.01
(version=TLSv1/SSLv3 cipher=OTHER);
Fri, 15 Jan 2016 06:15:02 -0800 (PST)
To: Buhake Sindi <buhake@gmail.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>
<CABUp4f4VPbDSyanidG3kWQ7GovGk1jf845=B7LwekS-1Ga2E_w@mail.gmail.com>
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <5698FEE5.9050305@gmail.com>
Date: Fri, 15 Jan 2016 14:15:01 +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: <CABUp4f4VPbDSyanidG3kWQ7GovGk1jf845=B7LwekS-1Ga2E_w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/x5ZiQ4q1WF7uGdJSkc_aC179Eo4>
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 14:15:06 -0000
Ouch, you are right, sorry for the confusion, Thanks, Sergey On 15/01/16 14:13, Buhake Sindi wrote: > Hi, > > Are you not mistaking this with RFC 7662? :-) > > Kind Regards, > > Buhake Sindi > > On 15 Jan 2016 12:34, "Sergey Beryozkin" <sberyozkin@gmail.com > <mailto: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 <mailto:OAuth@ietf.org> > https://www.ietf.org/mailman/listinfo/oauth > -- Sergey Beryozkin Talend Community Coders http://coders.talend.com/
- [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Brian Campbell
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Mike Jones
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Justin Richer
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Phil Hunt (IDM)
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation torsten
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Brian Campbell
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Bill Mills
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Antonio Sanso
- [OAUTH-WG] Question about RFC 7622 (Token Introsp… Sergey Beryozkin
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… John Bradley
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Sergey Beryozkin
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Buhake Sindi
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Sergey Beryozkin
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Buhake Sindi
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… John Bradley
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Vladimir Dzhuvinov
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Justin Richer
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Sergey Beryozkin
- Re: [OAUTH-WG] Question about RFC 7622 (Token Int… Sergey Beryozkin
- [OAUTH-WG] Status of draft-tschofenig-oauth-audie… Sergey Beryozkin
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Hannes Tschofenig
- Re: [OAUTH-WG] Mix-Up About The Mix-Up Mitigation Roland Hedberg
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Brian Campbell
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Mike Jones
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… John Bradley
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Nat Sakimura
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Mike Jones
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… John Bradley
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Mike Jones
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Nat Sakimura
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Sergey Beryozkin
- Re: [OAUTH-WG] Status of draft-tschofenig-oauth-a… Sergey Beryozkin