IETF Logo Mail Archive

Re: [OAUTH-WG] self-issued access tokens

Dick Hardt <dick.hardt@gmail.com> Fri, 01 October 2021 03:53 UTC

Return-Path: <dick.hardt@gmail.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 B10863A005E for <oauth@ietfa.amsl.com>; Thu, 30 Sep 2021 20:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 QPxoEVaYlmkw for <oauth@ietfa.amsl.com>; Thu, 30 Sep 2021 20:53:03 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 B2BE43A003C for <oauth@ietf.org>; Thu, 30 Sep 2021 20:53:02 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id g41so33326691lfv.1 for <oauth@ietf.org>; Thu, 30 Sep 2021 20:53:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UTI3tZ3McX82gtOGgbcPSLIk4j3rFDNvNNi98DYC6Rk=; b=MTTcyExjXfcD08Pm3RJTRgZd4ycXQp/Cizvk1mVx/kgDbK434QbEwfaFY/pwXqbJKd YiUlAU9Wj9COPnh6EFoK68DK0HWb9oroowbhQEG0fKCfAFNEi415yxUU51+DHU8UbHlu gjXSOmK0xatnOVK0DDqZbnyfp6rdaB02Q6wmIDCRdGPVlbmVIhE23Ea61Z5+LDFnzdLG xVGTV43Fd10Jn+9dJAZ/G1FJhGFwW7vUgPLkwUhVWBkpMxjmRhF3oeX6BwH4VWdgFRT0 HiIEsgIHSb5PC5IU271qN8xm9LYTdTM5t3hJmYoyfVbBuT/8wUYNR9a31coNnouXwcyr zmGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UTI3tZ3McX82gtOGgbcPSLIk4j3rFDNvNNi98DYC6Rk=; b=oKFbDTQCiv3l3B4SSJ/8FNfYeVGq7/Kb8aLbcK4PZGJwspP4Zi+3NXJH0OyM3z+rSI rsV53Ij3BDV2IaxIYoCy6J7rED/WzfI5Vw1jlzJucY4ibmY85b25dTBRH2tF0lFSKmic 9XNUKiQ15+jGw2UtPqV09v3H0Jwy+jKl44wwsoek+jNZDM4Adb71nS0s+hQ+IJjd+6Ri jrq4Cj5HbiG9R7LS/DHVSj96YOlbUHJbNY1RsoY5OMAnddahT8HpFGH1ciT5x9bn/K6d hcYZfEPmE1Glp6YmDLWxXGSWld6r9u+sypQhUIhdiUBU8R8+5o2mVqw6qlVkPGs+4Ufw vR+w==
X-Gm-Message-State: AOAM531QLef/DxSPyJ9AUlNEHXJD7BPXPvg1bDQXIBPk5HtJzQg0OHvF 2zyMBmVhUj43PjQW1sk5ZRXwnNGlT131AKdhfG0=
X-Google-Smtp-Source: ABdhPJxahWunrOXxnGAifzdIVKzSNMaNR+K3F4wCAjYT7i+k20aDfJ/44pFNbJt5JXiFi1OP1rNzXdY9lGjR/b7tElc=
X-Received: by 2002:a05:6512:3091:: with SMTP id z17mr3035019lfd.246.1633060380128; Thu, 30 Sep 2021 20:53:00 -0700 (PDT)
MIME-Version: 1.0
References: <TYCPR01MB567859999FB3350D6A1C63E5E5A99@TYCPR01MB5678.jpnprd01.prod.outlook.com> <CAD9ie-sgjUv3fppvTZvPpOyUKXo1H1i9LtkOk2yxzZ1+A+wt6w@mail.gmail.com> <TYCPR01MB56784381BE6799ADAA46E360E5AB9@TYCPR01MB5678.jpnprd01.prod.outlook.com>
In-Reply-To: <TYCPR01MB56784381BE6799ADAA46E360E5AB9@TYCPR01MB5678.jpnprd01.prod.outlook.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 30 Sep 2021 20:52:49 -0700
Message-ID: <CAD9ie-tMp44z_b=hG+OWC=Hc83RpC_WZ4AaerRMaOZ8cfEkDSg@mail.gmail.com>
To: toshio9.ito@toshiba.co.jp
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dab87b05cd427fe8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/3NnuYH7diVJ91d81Ob3n4ov2Zqo>
Subject: Re: [OAUTH-WG] self-issued access 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: Fri, 01 Oct 2021 03:53:08 -0000

Would be useful to understand your use case and what you the goals and
constraints are

On Thu, Sep 30, 2021 at 5:58 PM <toshio9.ito@toshiba.co.jp> wrote:

> Thanks Dick,
>
>
>
> I agree. The scenario of self-issued access tokens doesn't really follow
> the
>
> model of OAuth.
>
>
>
> So, if we do standardize self-issued access tokens, maybe OAUTH WG is not
> the
>
> right venue. Maybe HTTPBIS or HTTPAPI WGs?
>
>
>
>
>
> Toshio Ito
>
>
>
> *From:* Dick Hardt <dick.hardt@gmail.com>
> *Sent:* Wednesday, September 29, 2021 3:06 PM
> *To:* ito toshio(伊藤 俊夫 ○ＲＤＣ□ＩＴ研○ＣＮＬ) <toshio9.ito@toshiba.co.jp>
> *Cc:* oauth@ietf.org
> *Subject:* Re: [OAUTH-WG] self-issued access tokens
>
>
>
> If the client is sending a self-signed JWT to the RS, you essentially are
> just authenticating directly to the RS. Not really OAuth as the RS has not
> delegated authorization authority to the AS.
>
>
>
> If the client sends a self-signed JWT (a PAR) to the AS, and gets back an
> access token to present to the RS, you get centralized authorization
> decisions, a key feature of OAuth.
>
>
>
>
>
>
>

v2.35.0 | Report a Bug | By Email | System Status