IETF Logo Mail Archive

Re: [kitten] Re-authentication

Matthew Wild <mwild1@gmail.com> Mon, 30 January 2023 11:42 UTC

Return-Path: <mwild1@gmail.com>
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 2CDF8C169515 for <kitten@ietfa.amsl.com>; Mon, 30 Jan 2023 03:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.846
X-Spam-Level:
X-Spam-Status: No, score=-1.846 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSJZ_jflM_g1 for <kitten@ietfa.amsl.com>; Mon, 30 Jan 2023 03:42:01 -0800 (PST)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67D7DC169521 for <kitten@ietf.org>; Mon, 30 Jan 2023 03:42:01 -0800 (PST)
Received: by mail-oi1-x22f.google.com with SMTP id p133so9766729oig.8 for <kitten@ietf.org>; Mon, 30 Jan 2023 03:42:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qtn1o/gu73syE/jrDzbixTtvxKOhFPW80P6YU2ISPVA=; b=FebE+2oWBhuTDcvug/1Mb4x734fbANr//UuF/fat756VpBoJyRx7CKd07jPVLtvzUL 4gjYcVp83sERsxFiwiBMC6PnUHzQvnOWIi6ie5f+Int03uKTP0F6nOhVBJb645+fx1Pg AFh0iTQR58gCRwlR3jnuCoFvAFL+R2mLmN4KK3VzVlPR/TmyN5jxhp3j5wlXOGNbxISD rUDHADhZgQgoHUTIW46fqMWvfCBs6jyRYtzmI0X6YFiDGYYg1yqrBgicdzX+ptn2way4 8BhguLrdizqDANMrf5ieBRCL5kn4zw0VRkyV+XSHioL1y/uh+GenQzieeDZ3eJzDds4i 6Q1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qtn1o/gu73syE/jrDzbixTtvxKOhFPW80P6YU2ISPVA=; b=LnP1pFhTDLST+TIQ1w6h316ARvF0Qwx8j3CnAd5HwUr7UrKZ8PtPPlcILmpxk3EoWO p47Y3yFy+shpniENXEf1pPWs8ZM6El9985/9wWMBilmMt3daIEEthOmnuYZxtjt3fZrC NHIaYmQrnh1deljVwOqwpcSuyeksLYQ1GEnzIF+Ll7+i9R5pZZTJOUWiDZYy2a02WdXt XiLw+YZDWc9KBljMi4IIFVmwVKpUvetdGQOgaCOcIjes3DJD4FWy1XpU14aLCHHFudzN eixIOlgmcOOKYqj3mzxHF0M8hiqQeiIydgniePNTaifzNuzU+HIGMvN94w73JTqJu7WG AKpw==
X-Gm-Message-State: AO0yUKXcGTD3vAgj8AxOkEtxc+JubiFBmWxaJkN38YSM+AvXL3OJjLlR Ona+6gqVFQKaTjG2bBldf/ApPUlgV9vAztF/HvT70z+I4OY=
X-Google-Smtp-Source: AK7set96QvicNv4/qgG5k6yaCtrgLyLcmWTNYTxCDAnnoz5yp6uU06jEuDgjV1rVumdsUfRgrH2AGf1VW83TfnaRYgI=
X-Received: by 2002:aca:ba41:0:b0:378:6ae3:dd47 with SMTP id k62-20020acaba41000000b003786ae3dd47mr76820oif.71.1675078920455; Mon, 30 Jan 2023 03:42:00 -0800 (PST)
MIME-Version: 1.0
References: <CAJt9-x6gz+0tqsheAYFZLyERcVZi_rt0HaF0=vPJ5OOiCYHzdA@mail.gmail.com> <d2d8e99c-7d5b-badc-f2a5-ff182c8ee9aa@isode.com>
In-Reply-To: <d2d8e99c-7d5b-badc-f2a5-ff182c8ee9aa@isode.com>
From: Matthew Wild <mwild1@gmail.com>
Date: Mon, 30 Jan 2023 11:41:48 +0000
Message-ID: <CAJt9-x6CjWycrUkeoD3p46ObowfHOLWrqzF=wwmsnF7bVr-0_g@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: kitten@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/bijQZg3fAB7tRhl0Jntz_NKLas0>
Subject: Re: [kitten] Re-authentication
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: Mon, 30 Jan 2023 11:42:05 -0000

On Mon, 30 Jan 2023 at 10:36, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
> On 29/01/2023 12:33, Matthew Wild wrote:
> > With the MFA and FAST stuff recently discussed, and other token
> > mechanisms such as OAUTHBEARER, some sessions will typically have
> > reduced permissions. For example, a server may require the client to
> > authenticate with a password in order to perform certain
> > administrative tasks relating to the user's account. Therefore we'd
> > need a way for a token-authed session to upgrade to a password-authed
> > one.
> I am curious about signalling mechanism for this.

My current thoughts for XMPP are to extend the not-authorized error
condition: https://www.rfc-editor.org/rfc/rfc6120.html#section-8.3.3.11

It would add an extra flag that informs clients reauthentication is
possible, to continue past the error. The reauth bit itself, I'm not
entirely clear on yet.

For example, I suspect reauth should be limited to credentials of the
current user. Switching the user of an active session in a stateful
protocol such as XMPP would be a path full of pitfalls.

Thanks for the pointers to LDAPv3, I'll give it a read and see if
anything is applicable.

Regards,
Matthew

v2.23.0 | Report a Bug | By Email