IETF Logo Mail Archive

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

Greg Hudson <ghudson@mit.edu> Sun, 21 November 2021 19:19 UTC

Return-Path: <ghudson@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 2A7653A0541 for <kitten@ietfa.amsl.com>; Sun, 21 Nov 2021 11:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.351
X-Spam-Level:
X-Spam-Status: No, score=-3.351 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-1.852, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 7v2q0I2IQNVD for <kitten@ietfa.amsl.com>; Sun, 21 Nov 2021 11:19:40 -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 A76AC3A00D7 for <kitten@ietf.org>; Sun, 21 Nov 2021 11:19:40 -0800 (PST)
Received: from [18.30.133.57] ([18.30.133.57]) (authenticated bits=0) (User authenticated as ghudson@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1ALJJaEd020889 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Sun, 21 Nov 2021 14:19:37 -0500
To: Sam Hartman <hartmans-ietf@mit.edu>, kitten@ietf.org
Cc: Pavel Březina <pbrezina@redhat.com>
References: <0100017d06db6c83-21cbd2ce-f371-48a9-88ce-5b6452842241-000000@email.amazonses.com> <99094d0b-6bc1-d896-4f70-83f2e1696eb3@mit.edu> <0100017d351e67c9-dc6040a5-6e14-4d36-ba07-815290f9f8c3-000000@email.amazonses.com>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <3ff4dce4-b9a3-8324-ae15-8951608aede3@mit.edu>
Date: Sun, 21 Nov 2021 14:19:36 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <0100017d351e67c9-dc6040a5-6e14-4d36-ba07-815290f9f8c3-000000@email.amazonses.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/qoKlYzfHAWred6uNyt620Wi4q84>
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: Sun, 21 Nov 2021 19:19:43 -0000

On 11/18/21 5:15 PM, Sam Hartman wrote:
> 1) We agree on a name for the preauth constant that makes it clear this
> is either Redhat or FreeIPA specific or something like that.
> 
> 2) You track the security concerns and when you eventually produce
> documentation explain the use case in a way that scopes it to a use case
> where the protocol is safe
> 
> 3) Without waiting for 2, I approve the registration.

I think this is reasonable, and the name PA-REDHAT-IDP-OAUTH2 proposed
by Pavel seems fine.

v2.23.0 | Report a Bug | By Email