Re: [OAUTH-WG] JWT Response for OAuth Token Introspection and types of tokens
Warren Parad <wparad@rhosys.ch> Sun, 07 February 2021 23:56 UTC
Return-Path: <wparad@rhosys.ch>
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 9924E3A0C30 for <oauth@ietfa.amsl.com>; Sun, 7 Feb 2021 15:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rhosys.ch
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 XPmksY1IvUNs for <oauth@ietfa.amsl.com>; Sun, 7 Feb 2021 15:56:31 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 C12593A0C28 for <oauth@ietf.org>; Sun, 7 Feb 2021 15:56:31 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id n201so13172342iod.12 for <oauth@ietf.org>; Sun, 07 Feb 2021 15:56:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rhosys.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zvZ3ygq6UFw3PKenL0MI2QZjDzjYCIKs1Yw7haUwyL8=; b=KcDtqOTVukPxx+9MMOByxyexPTGLsz4VujTckbWaq4uYOu0h+n8jT7wLmpoVLjJXoe K7epF3osCZ4oUq2MlYSLMNHzy9ZRtoMiQv+FNxxHuNBOTkxdTkP0DGXhwXCUYT6pvxvl qe+xffQotBS/ucE2srXjzO+y1cJcJXs0yxAhmqwZoMGW8OMdXQPj95CJpjn/sIG8nVF6 EbQ0wPVXAahx7sLR7ziYngz7quWacjVxgQSMeL92MwmyP6OhU7nVX5U5HRrjUD6wgjRb wzpaMjjaV2Xy21IEJ92yV0/KnmliVS3eH7zigl2rZvPLxnNLjN9FwGI1m3gA2MgBUsMU o/DA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zvZ3ygq6UFw3PKenL0MI2QZjDzjYCIKs1Yw7haUwyL8=; b=BP85JM+yNexmCWEG8or6rk6nQP5KUospAPdFaYEQcug7Hosr0UwXwIippO3PEhJt/2 diMF149nfx9mfSPF2M64hFgyA35/iXqskoCumlFnRWEmORy5SriJ1gV0lFq4NGOuz7bI KJ4q1j/vuD2QeSbVtvWD1q00T7KQ03ZgYJ07I+zHZXqZgKIxgrA+kV2h96Y1pb1AkGEi 2/lmP71SzYQtR0dd0T32SImN0cLNyaO5GViPUw+2YtHYZSKJZY74Ww//iFSi96gUq0iF pEb9hYCb3QtZ0HrYuQPeR3RNRJC1EvGtnfbX0VaY3kYdrlggoN9mO0Kr8GRaOn3tA3PP U7Hw==
X-Gm-Message-State: AOAM532imR/T68x3p1ac/ED9CY1v0/s0iEO1vQkoceZbmNDUv1F4av88 cnAI82nThOJbNoDUXDWwhtKNdVV8Pr8NAS5sK7Ek
X-Google-Smtp-Source: ABdhPJzLwj9JfbVcCCx5T2XcEIiVWgNeoW7o3URh6vOeVRKDaDReFGrDMUJFr0tOkb+Kddf79exbC15FqopCmDlwdoY=
X-Received: by 2002:a02:5447:: with SMTP id t68mr11046283jaa.78.1612742190681; Sun, 07 Feb 2021 15:56:30 -0800 (PST)
MIME-Version: 1.0
References: <CALkShcuu6dR2=SqAaVZTTm2zjqQPA4MtvswUQmn-2_vqE2w8Yg@mail.gmail.com> <536313C1-95E8-4A05-97B1-F3CD8984B49F@lodderstedt.net>
In-Reply-To: <536313C1-95E8-4A05-97B1-F3CD8984B49F@lodderstedt.net>
From: Warren Parad <wparad@rhosys.ch>
Date: Mon, 08 Feb 2021 00:56:20 +0100
Message-ID: <CAJot-L05Nb5FQQ_OOgW_s4Mswo0GW3-j7HTTxtbR2OgqESijWg@mail.gmail.com>
To: Torsten Lodderstedt <torsten=40lodderstedt.net@dmarc.ietf.org>
Cc: Andrii Deinega <andrii.deinega@gmail.com>, oauth <oauth@ietf.org>, draft-ietf-oauth-jwt-introspection-response@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006417b305bac7cd8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/3xyRdc0CmO4ZX21lfcSImfHIHjs>
Subject: Re: [OAUTH-WG] JWT Response for OAuth Token Introspection and types of tokens
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, 07 Feb 2021 23:56:36 -0000
> > I‘m therefore leaning towards explicitly stating in our draft that it is > not intended to be used with refresh tokens. I'm not following, why explicitly state that it isn't intended. If an AS wants to provide a similar JSON response to a query with the refresh token, why not encourage that? Warren Parad Founder, CTO Secure your user data and complete your authorization architecture. Implement Authress <https://authress.io>. On Sun, Feb 7, 2021 at 10:58 PM Torsten Lodderstedt <torsten= 40lodderstedt.net@dmarc.ietf.org> wrote: > Hi Andrii, > > Am 07.02.2021 um 21:30 schrieb Andrii Deinega <andrii.deinega@gmail.com>: > > > Hi Torsten, > > thank you for your response. > > My use case is pretty straight forward > > An OAuth client queries the AS to determine the active state of an access > token and gets the introspection response which indicates that this access > token is active (using RFC7662). > > An OAuth client queries the AS to determine the active state of a refresh > token and gets the introspection response which indicates that this refresh > token is active (using RFC7662). > > An OAuth client queries the AS to determine the active state of an access > token and gets the introspection response (JWT) which indicates that this > access token is active (using this draft). > > Now, an OAuth client queries the AS to determine the active state of a > refresh token (using this draft)... How will the introspection response > look like assuming that the client provides the valid refresh token and > technically, nothing stops it from doing so. > > > why should the state be provided as JWT?I think the plain JSON response is > sufficient in that case. I also think using token introspection for > checking the state of a token from the client side has limited utility. The > definitive decision is always made when the client tries to access a > resource. > > I‘m therefore leaning towards explicitly stating in our draft that it is > not intended to be used with refresh tokens. > > best regards, > Torsten. > > > Regards, > Andrii > > > On Sun, Feb 7, 2021 at 4:14 AM Torsten Lodderstedt < > torsten@lodderstedt.net> wrote: > >> Hi Andrii, >> >> thanks for your post. >> >> The draft is intended to provide AS and RS with a solution to exchange >> signed (and optionally encrypted) token introspection responses in order to >> provide stronger assurance among those parties. This is important in use >> cases where the RS acts upon the introspection response data and wants the >> AS to take liability re the data quality. >> >> I’m not sure whether there are similar use cases if a client introspects >> a refresh token. What is your use case? >> >> best regards, >> Torsten. >> >> > Am 07.02.2021 um 08:41 schrieb Andrii Deinega <andrii.deinega@gmail.com >> >: >> > >> > Hi WG, >> > >> > draft-ietf-oauth-jwt-introspection-response-10 states that "OAuth 2.0 >> Token Introspection [RFC7662] specifies a method for a protected resource >> to query an OAuth 2.0 authorization server to determine the state of an >> access token and obtain data associated with the access token." which is >> true. Although, according to RFC7662, the introspection endpoint allows to >> introspect a refresh token as well. Hence, the question I have is how will >> a token introspection response look like when the caller provides a refresh >> token and sets the "Accept" HTTP header to >> "application/token-introspection+jwt"? >> > >> > I expect there will be no differences, right? >> > >> > If so, I suggest to >> > • replace "a resource server" by "the caller" in section 4 >> (Requesting a JWT Response) >> > • change "If the access token is invalid, expired, revoked" by >> "If a given token is invalid, expired, revoked" in section 5 (JWT Response) >> > If not, my suggestion would be to clarify what the AS should do when it >> asked to introspect the refresh token in general and additionally, what >> should happen in the same case based on the type of the caller from the >> AS's point of view. >> > >> > Regards, >> > Andrii >> > >> >> _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- [OAUTH-WG] JWT Response for OAuth Token Introspec… Andrii Deinega
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Torsten Lodderstedt
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Andrii Deinega
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Torsten Lodderstedt
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Warren Parad
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Torsten Lodderstedt
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Warren Parad
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Vladimir Dzhuvinov
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Warren Parad
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Vladimir Dzhuvinov
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Andrii Deinega
- Re: [OAUTH-WG] JWT Response for OAuth Token Intro… Vladimir Dzhuvinov