IETF Logo Mail Archive

Re: [kitten] Stating support for HTTP-SASL on the HTTP WG list

Rick van Rein <rick@openfortress.nl> Tue, 07 February 2023 10:35 UTC

Return-Path: <vanrein@vanrein.org>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA1ADC140C05 for <kitten@ietfa.amsl.com>; Tue, 7 Feb 2023 02:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.666
X-Spam-Level:
X-Spam-Status: No, score=-5.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, PDS_RDNS_DYNAMIC_FP=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBTMsnNUb_B2 for <kitten@ietfa.amsl.com>; Tue, 7 Feb 2023 02:35:44 -0800 (PST)
Received: from fame.vanrein.org (2a02-58-157-9b00--7.ip6.tweak.nl [IPv6:2a02:58:157:9b00::7]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 557A1C140C04 for <kitten@ietf.org>; Tue, 7 Feb 2023 02:35:43 -0800 (PST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id 9CF232C8F8; Tue, 7 Feb 2023 10:35:42 +0000 (UTC)
Date: Tue, 07 Feb 2023 10:35:42 +0000
From: Rick van Rein <rick@openfortress.nl>
To: Nico Williams <nico@cryptonector.com>
Cc: Simo Sorce <simo@redhat.com>, kitten@ietf.org
Message-ID: <20230207103542.GD30583@openfortress.nl>
Mail-Followup-To: Nico Williams <nico@cryptonector.com>, Simo Sorce <simo@redhat.com>, kitten@ietf.org
References: <20230127160101.GB635@openfortress.nl> <048e6943f02302bb5cf7b8c55521931ce3748d30.camel@redhat.com> <Y9TF+tM+J07Vbcrn@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Y9TF+tM+J07Vbcrn@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/bRpVrCNsibO6W40tBbzL_qLcds4>
Subject: Re: [kitten] Stating support for HTTP-SASL on the HTTP WG list
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2023 10:35:45 -0000

Hi,

> > The last thing we need is for people to invent their own caching
> > mechanisms to prevent browsers or other client from constantly
> > prompting for credentials on naive configurations.
> 
> There must be generic cookie construction schemes out there.  It'd be
> nice to have a standard, but obviously much cookie contents beyond
> obvious things like expiration times is going to all be application-
> specific.

Agreed.  I defined "s2s" alongside "200 OK" approval as a token, but
a generic mechanism is better.  OAuth2 introduced Bearer tokens for
that purpose, functionally similar to cookies.

-Rick

v2.23.0 | Report a Bug | By Email