Re: [kitten] Kerberos Preauth Registration for OAuth2 device flow

Benjamin Kaduk <kaduk@mit.edu> Fri, 19 November 2021 01:51 UTC

Return-Path: <kaduk@mit.edu>
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 F011C3A00D5 for <kitten@ietfa.amsl.com>; Thu, 18 Nov 2021 17:51:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 yFgn2zrGYzS8 for <kitten@ietfa.amsl.com>; Thu, 18 Nov 2021 17:51:47 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8741B3A00D4 for <kitten@ietf.org>; Thu, 18 Nov 2021 17:51:47 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1AJ1pdUs030653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Nov 2021 20:51:44 -0500
Date: Thu, 18 Nov 2021 17:51:38 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: Greg Hudson <ghudson@mit.edu>, kitten@ietf.org, Pavel Březina <pbrezina@redhat.com>
Message-ID: <20211119015138.GK93060@kduck.mit.edu>
References: <0100017d06db6c83-21cbd2ce-f371-48a9-88ce-5b6452842241-000000@email.amazonses.com> <99094d0b-6bc1-d896-4f70-83f2e1696eb3@mit.edu> <tslczmx6rgl.fsf@suchdamage.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <tslczmx6rgl.fsf@suchdamage.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/38P4QE3B8QtJPzMD92vRbG39lW8>
Subject: Re: [kitten] Kerberos Preauth Registration for OAuth2 device flow
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 19 Nov 2021 01:51:50 -0000

Thanks all for the great discussion so far.

On Thu, Nov 18, 2021 at 03:15:22PM -0700, Sam Hartman wrote:
> >>>>> "Greg" == Greg Hudson <ghudson@mit.edu> writes:
> 
>     Greg> On 11/9/21 5:39 PM, Sam Hartman wrote:
>     >> On the interoperability side, the protocol between the KDC and
>     >> the OAuth provider does not appear to be described at all.  You
>     >> get vendor lockin between a KDC and OAuth provider as far as I
>     >> can tell.
> 
>     Greg> Preauth mechs don't generally specify back-end protocols;
>     Greg> certainly RFC 6560 does not.
> 
> I think it's the first preauth mechanism where that was an issue.
> My thoughts at the time reading the draft was that the kind of tokens
> used for OTP were fairly well understood  and it wasn't a big deal.
> 
> I think my answer here is that I personally don't mind the  backend
> protocol being out of scope, and no one else in the WG seems to mind
> either, so it is okay.

While I personally would prefer to specify the backend protocol, I think
that the current trends in the IETF are that this kind of backend protocol
does not need to be fully specified.

-Ben