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

John Bradley <ve7jtb@ve7jtb.com> Fri, 15 January 2016 13:32 UTC

Return-Path: <ve7jtb@ve7jtb.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 680AB1A0196 for <oauth@ietfa.amsl.com>; Fri, 15 Jan 2016 05:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 BsrlfLn1AKVV for <oauth@ietfa.amsl.com>; Fri, 15 Jan 2016 05:32:36 -0800 (PST)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d: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 06C9D1B2CDD for <oauth@ietf.org>; Fri, 15 Jan 2016 05:32:35 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id y67so53385306qkc.2 for <oauth@ietf.org>; Fri, 15 Jan 2016 05:32:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0IdEJUlT5CrBpEi1NkKkpmqPwStxq4ExniDgbH/cV2c=; b=v9G+z+iqOdZjkbPpJW448TUjbjy1hHYeiQVz0xjbDbrB4KRbumL7shH1g16Q6idDjB 4mi8nXj6m/jIRY+M01mXBMl6zYdFgL9eJI/nxgptrkFvGFVtE4dBm9gjzAbXHCY9Kc87 3Nq+d4SWXDSIuJCH2iFgAqoy8gEFHbaQrepi6wQoUyIG3Uj0I0/LRnsu1MoZDbIXsh2V ByGxyBwS0JgYS/Igz57TNtxXcRih7np/LU5qP3cyOligjxCzVY/GiXa4TSAnYpm6TUcT 7wBjL0X2ytHxDD69kbNqDCF12EyWb3V4mOSl1TUbwaDNWrF7C+w4xS58p57ZBLR/uhvG gIvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=0IdEJUlT5CrBpEi1NkKkpmqPwStxq4ExniDgbH/cV2c=; b=g9QmHpxF8e+ZbloIdJL/LGy77nsEjoFEuwktVWMLOY2j4WxBGDr+ydTZvCW+OZivWl TDSlvafPnG1c43KuiojtwNUK9J+2a7Q3x7ZnbHQSeoqBhu1YJm1bWbdywd/NbrV8dc9l IfZAWTe5TfxkvCTb2ccKMKebk5Z0bL2Po6HLqo76S0S1vybSNRVAxXcWNLBTAu1cSA8l fCzc2oxzNuA5B31mIo/caA04cXI8UqMbg4s7GCiTNy+yZwyg1gGsla7K9HZ4fti5MEfL NVVAiH//NAQlwHuaw0Re1GB5BmVWqLnsHQHPhwtZyRLDZdiUXGmHHFjXm/OkV9d6g7h5 iquQ==
X-Gm-Message-State: ALoCoQm37RPbeo3eIr5iWyQMYx4g1a7u+D5k+mTtoGiM9ycRv5Mpf9TCGl1uTRaOaCR59NHagoGku20mbHxYk91oXMuk3n2urw==
X-Received: by 10.55.18.76 with SMTP id c73mr12563302qkh.54.1452864755129; Fri, 15 Jan 2016 05:32:35 -0800 (PST)
Received: from [107.17.140.60] ([107.17.140.60]) by smtp.gmail.com with ESMTPSA id j69sm4532684qkh.21.2016.01.15.05.32.34 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 15 Jan 2016 05:32:34 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <5698CB3D.1030306@gmail.com>
Date: Fri, 15 Jan 2016 08:32:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <69B0E23E-818A-4FE4-81A0-A8106EB6C312@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>
To: Sergey Beryozkin <sberyozkin@gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/i9aK7AdSDJL9TqA1WeN-WQNnIcw>
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:32:38 -0000

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