Re: [OAUTH-WG] MTLS and in-browser clients using the token endpoint

Brian Campbell <bcampbell@pingidentity.com> Fri, 01 February 2019 21:31 UTC

Return-Path: <bcampbell@pingidentity.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 3B7DF131309 for <oauth@ietfa.amsl.com>; Fri, 1 Feb 2019 13:31:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.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 t_Z5opXn-lOQ for <oauth@ietfa.amsl.com>; Fri, 1 Feb 2019 13:31:06 -0800 (PST)
Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 D5652130F03 for <oauth@ietf.org>; Fri, 1 Feb 2019 13:31:03 -0800 (PST)
Received: by mail-it1-x134.google.com with SMTP id g85so11548497ita.3 for <oauth@ietf.org>; Fri, 01 Feb 2019 13:31:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FIkIh8Gsv9220efgOJQyWKJ4crtqMAwNtlK8SV8hArk=; b=Ocs8uHK+nIdzKwchIWK2lUhlY9acL5fvaxo8l6ewwXCHXXepx8g58lwWY9BP4XVbom bUOJXNrx/oKVFxs1d7B+uBszxmf9+PaIOaC6uc4PspVTajaHVzOgtOHoG3Q+854zuD0x 03MqG3EOoYjh6qWb8y4VRtTxbteg0NacOBXcI=
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=FIkIh8Gsv9220efgOJQyWKJ4crtqMAwNtlK8SV8hArk=; b=VKed8oW/FR7VmLP8mU3RUu/eI3FROUh8tPr3FkFnbAOGWfoMG9F+F/QzHd2YyunJcv RmlwWk6AxvpCrC6Z7d479tzBdjPrQCO+28Lj1NSAC48BRHGHvWsTQu0Gu9E0PLBYBlrj U1l3PW0V5gpuLQqIq87OZCb0lvPJ2D5weyTsln054xVgs/SEErCPxV7yE8V1ikPfuBDM pSNMwb+DmcT/aJw1QU5X7ImkaS1L0JTvmDou6VAEvIzdHW68VK15FGPOagWuMH2uLkeq nanfnPjjMHXI7NyvPecjbhA05MQgZZoyavmiadMv0Vr1uG2pIqxFZCSwyt2DzGjwIcJZ hGLw==
X-Gm-Message-State: AJcUukeHfhVEi7b0Mfu5UtqIrZbSbSJvSjCYi+afZh3gVSNyIVAIAR4E uQMnlrTHYVNz4tAp1kkx2kLcq/jojMf8zdwOkW6Uqlm3eA+GZlBqhv4zZY78GNeOP3uh7SolIaz 5a4cvj8ZoB0pj+cmU
X-Google-Smtp-Source: ALg8bN7Jwe0REMXrYohdJo3tLQwVFNq4iZmDz6z9HNf+RpJSPqf70dgbCYDFW2BQEQd5R8MNHRSeO9Qlm56zm6WvIAQ=
X-Received: by 2002:a02:5f9d:: with SMTP id x29mr27464395jad.28.1549056663097; Fri, 01 Feb 2019 13:31:03 -0800 (PST)
MIME-Version: 1.0
References: <CA+k3eCTKSFiiTw8--qBS0R2YVQ0MY0eKrMBvBNE4pauSr1rHcA@mail.gmail.com> <6A614742-290D-47E2-B3E9-A4D49DB32DD7@forgerock.com> <CA+k3eCSoNRGrsxeLYd6DEqU+U6TB_aXV2aPUa07Um2X0ZH_ZEw@mail.gmail.com> <548FF68E-7775-4FE0-829F-1E9CC6EA8E3F@alkaline-solutions.com> <1119DDAE-8044-43C9-A6D4-6032B3BB62B8@forgerock.com> <9D007408-3BCC-4165-BCA4-083BD7602E7D@alkaline-solutions.com> <CA+k3eCQi1sz2bDOMEATpN9ZvXd+VJydQXG03WKuLczG5kz2z+Q@mail.gmail.com> <CAP-T6TTD-nLGoPHqJ042SzotLorb2mzoWgLxsausWHhRPZr8xA@mail.gmail.com> <CA+k3eCQtgku68usoCFsTeHVnNOLqWs6NweOgpQKsa7_9=wK7Vw@mail.gmail.com> <99d38517-0e25-789f-83ae-9f33e5620475@aol.com>
In-Reply-To: <99d38517-0e25-789f-83ae-9f33e5620475@aol.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Fri, 01 Feb 2019 14:30:36 -0700
Message-ID: <CA+k3eCQVL4DeRqHWYu6=xXjBK2RnukQ5RxFzRjGZYr4au8bBkQ@mail.gmail.com>
To: George Fletcher <gffletch=40aol.com@dmarc.ietf.org>
Cc: Dave Tonge <dave.tonge@momentumft.co.uk>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002430580580dbdc50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/t305fOl9YKGJ3kLRE57e6sck9IM>
Subject: Re: [OAUTH-WG] MTLS and in-browser clients using the token endpoint
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: Fri, 01 Feb 2019 21:31:12 -0000

Yes, that would work.

On Fri, Feb 1, 2019 at 2:28 PM George Fletcher <gffletch=
40aol.com@dmarc.ietf.org> wrote:

> What if the AS wants to ONLY support MTLS connections. Does it not specify
> the optional "mtls_endpoints" and just use the normal metadata values?
>
> On 1/15/19 8:48 AM, Brian Campbell wrote:
>
> It would definitely be optional, apologies if that wasn't made clear. It'd
> be something to the effect of optional for the AS to include and clients
> doing MTLS would use it when present in AS metadata.
>
> On Tue, Jan 15, 2019 at 2:04 AM Dave Tonge <dave.tonge@momentumft.co.uk>
> wrote:
>
>> I'm in favour of the `mtls_endpoints` metadata parameter - although it
>> should be optional.
>>
>
> *CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s). Any
> review, use, distribution or disclosure by others is strictly prohibited..
> If you have received this communication in error, please notify the sender
> immediately by e-mail and delete the message and any file attachments from
> your computer. Thank you.*
>
> _______________________________________________
> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>
>
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._