Re: [OAUTH-WG] Refreshing tokens on the RS

Jared Jennings <jaredljennings@gmail.com> Sun, 10 May 2020 20:14 UTC

Return-Path: <jaredljennings@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 B94D63A0B7D; Sun, 10 May 2020 13:14:56 -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 qS6hoghrGfcH; Sun, 10 May 2020 13:14:55 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 B15A23A0B7C; Sun, 10 May 2020 13:14:54 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id o10so6104313ejn.10; Sun, 10 May 2020 13:14:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i2+LLcDtwAdbRZ4bfBbom3nOYpICMCjlODBzBaPGrBY=; b=EVkPx/zQqVawTTYTIygZffgDzzMQRPsvhfC96BlCscWA++q6lLlbT+UXBOmWdnnkRp nBil4Awen/y8yxNA6iuYAZ3YxFqwlLbaOilyKoEvK+TkpDaj+Cssro2pOWbGLBisqZrg HKTDnr2Q/vkIYImcFQlRzdhp3Klr4JA2CoUYsY2KOh1W/xGjN6Dxh3lLHi1bS6hf19Do seIt6WIKuafWRex+JujRaNgdYXIx0P3Mz06g/sSWQtvEkuJrq5JFcVmlQTsusaCNuJun HDrF7zBgMksJXs/eNLxIa5te8qdKyvPJiTC7IC7JjNZFwI7yVfxz0pzfUE8m2/9WT2ps R2bA==
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=i2+LLcDtwAdbRZ4bfBbom3nOYpICMCjlODBzBaPGrBY=; b=T/KjnF5lDM8oymE4bysYEVrtetqyJtgqu8REvPa//1fdHDb7s5Ry1BuJSpXc2rcYpk TfzOqPPuPM1ytlcLVM8+Z2D8fbzx2IHUmteyOUr0aMsLbYRo0G9KAGB+EDD7oncbFaqu w0dOJEz6wZv4Lz/EeVhupu7t0xeF4w68TLzI4mCWQe0Fk09Npd/f2nmx5x7Fmdve3yA8 5w0JdkdmRoQKmrAEJxujpSDncobGAWYAm+sNv/sZBSKNYLXRUfYbM3NLnRT4Q72/+MUJ RoyNASq0zmqPccW9Pvi2tS0BMqUN5mGlvp8pAe4B39d463pY39HncuaW5zkjpcg1a1m0 dgFA==
X-Gm-Message-State: AGi0Pub3/kkhjinqbyEjZY85L3IxLf2SCUJ9zJKnIw7EWM2shzTjgsXA cSdBEIddWAVut12oiD+Xi3chLlGG2pVdupZi229oES4Houk=
X-Google-Smtp-Source: APiQypJPTUhOLOjlTH+1BIQmTCTzZYnVJsHuzb/tDXYusE2JRFpLs05lbuTSb2VCP9+sI1oBP7nV+/yDdWn0mKi3nLU=
X-Received: by 2002:a17:907:4420:: with SMTP id om24mr9975521ejb.99.1589141693083; Sun, 10 May 2020 13:14:53 -0700 (PDT)
MIME-Version: 1.0
References: <033601d622f0$7869bfa0$693d3ee0$@augustcellars.com>
In-Reply-To: <033601d622f0$7869bfa0$693d3ee0$@augustcellars.com>
From: Jared Jennings <jaredljennings@gmail.com>
Date: Sun, 10 May 2020 15:14:40 -0500
Message-ID: <CAMVRk+JfvCzgVCZ_jbLQ9ZT4q3En0uK+5h02-q=untVHvn19nA@mail.gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
Cc: oauth <oauth@ietf.org>, draft-ietf-ace-oauth-authz@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001d34f605a550e2ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Y1NMfwmWu801kzrONmDb3_78Xvo>
Subject: Re: [OAUTH-WG] Refreshing tokens on the RS
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, 10 May 2020 20:14:57 -0000

Not exactly the same, but seems similar to some of the proposed logic in
https://tools.ietf.org/wg/oauth/draft-ietf-oauth-incremental-authz/

-Jared
Skype:jaredljennings
Signal:+1 816.730.9540
WhatsApp: +1 816.678.4152


On Tue, May 5, 2020 at 10:19 AM Jim Schaad <ietf@augustcellars.com> wrote:

> Over in the ACE working group we are currently having a discussion about
> refreshing tokens on an RS.  I want to make sure that this is not something
> that this working group has already solved.  The basic scenario is:
>
> 1.  Client gets token T1 and posts it to the RS
> 2.  After some time the RS returns and error to the client about an access
> issue
> 3.  Client gets a new token from the AS T2, possibly using a refresh token.
> 4. Client posts the token T2 to the RS
> 5.  The RS somehow needs to associate token T1 and T2 for long term
> security
> sessions.
>
> I do not believe that OAuth has this issue because there is not currently
> any concept that a token is used for anything other than a single
> request/response between the client and the RS.  There is no idea of the RS
> storing tokens long term associated with a TLS session that might need to
> have the access rights for that TLS session changed.
>
> Please provide any feedback that you might have.
>
> Thanks
> Jim
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>