IETF Logo Mail Archive

Re: [OAUTH-WG] Listing OAuth Access Token Metadata

David Waite <david@alkaline-solutions.com> Sun, 03 April 2022 06:35 UTC

Return-Path: <david@alkaline-solutions.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0223C3A1A92 for <oauth@ietfa.amsl.com>; Sat, 2 Apr 2022 23:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alkaline-solutions.com
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 Eu6TW3uYPblJ for <oauth@ietfa.amsl.com>; Sat, 2 Apr 2022 23:35:19 -0700 (PDT)
Received: from caesium6.alkaline.solutions (caesium6.alkaline.solutions [157.230.133.164]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45B6C3A1A91 for <OAuth@ietf.org>; Sat, 2 Apr 2022 23:35:18 -0700 (PDT)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by caesium6.alkaline.solutions (Postfix) with ESMTPA id 65F78206E8A; Sun, 3 Apr 2022 06:35:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alkaline-solutions.com; s=dkim; t=1648967717; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=vzpghKgdwxW7C/qylDVdM9XrTnZ83DvnBgdMvsNMlyc=; b=VYJGgMiO7YZfx/bdyjIWtKiDfbVz9Aj7uFAGUgWpXRCfB69KpeUxYnqHIot4uaObUWGgGv wKnFnZkRdG/B9/tegPBSLi2buzlGeWGl7oRuWRjLDV+L7XD9KMn1BAnBK78ZOnhD8YyETS s4FGQi25invRuaDvA1z/SnaxaVJv6qU=
From: David Waite <david@alkaline-solutions.com>
Message-Id: <CF00B22F-0F92-4578-82DA-7EBF0208F4C6@alkaline-solutions.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2EBB2ACE-032A-46EA-98B2-610C9D0A578A"
Mime-Version: 1.0
Date: Sun, 03 Apr 2022 00:35:15 -0600
In-Reply-To: <CAL4nJSZSAEQQOy0dEwwD88Ne+vsQfTmj_RM7MPAFHnd18D7wMA@mail.gmail.com>
Cc: OAuth@ietf.org
To: Dhaura Pathirana <dhaurapathirana@gmail.com>
References: <CAL4nJSZSAEQQOy0dEwwD88Ne+vsQfTmj_RM7MPAFHnd18D7wMA@mail.gmail.com>
Authentication-Results: caesium6.alkaline.solutions; auth=pass smtp.mailfrom=david@alkaline-solutions.com
X-Spamd-Bar: /
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/YEDFTXPboqRJKD129-NnuyfvHcA>
Subject: Re: [OAUTH-WG] Listing OAuth Access Token Metadata
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 03 Apr 2022 06:35:24 -0000

> On Apr 1, 2022, at 3:24 AM, Dhaura Pathirana <dhaurapathirana@gmail.com> wrote:
> 
> I would like to know if anyone has seen this (listing token metadata) as a common use case in OAuth2 and a standard way of doing it had been proposed before? 

OAuth Token Introspection (RFC 7662) defines a way to query for active state and meta-info.

However, its use is defined only for protected resources, and not the resource owner or the client the token was issued to. 

-DW

v2.23.0 | Report a Bug | By Email