[Jmap] Question about authentication discovery
"Matt Hogan" <matt@mtthgn.com> Fri, 24 January 2020 13:16 UTC
Return-Path: <matt@mtthgn.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32BE3120044 for <jmap@ietfa.amsl.com>; Fri, 24 Jan 2020 05:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtthgn.com header.b=Ml0mjlY3; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ssagXgpI
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 AWWkqjmJC6dD for <jmap@ietfa.amsl.com>; Fri, 24 Jan 2020 05:16:53 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0BD912003E for <jmap@ietf.org>; Fri, 24 Jan 2020 05:16:52 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 2F37175C for <jmap@ietf.org>; Fri, 24 Jan 2020 08:16:52 -0500 (EST)
Received: from imap1 ([10.202.2.51]) by compute4.internal (MEProxy); Fri, 24 Jan 2020 08:16:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtthgn.com; h= mime-version:message-id:date:from:to:subject:content-type; s= fm1; bh=vSeoIWMX5W2748vJK/OHR5PP8Irf45HCcLmaRrfN1L8=; b=Ml0mjlY3 kVRr6YW5TCxUcreDGEE+h/n0UuXR7K+LgsN91hvxAR1Yll3q5INLoqo6zO4/ptRv jUcjbHOA4MfGr/xwJFfyT6ZBfHA5OiiV5X9Z5PTzukf+7Bid5pk3vjCjxvwTdRny 1806B2njgOjsbAFjsqmVhLME9VHl4aMtAtCBXnVHUWZd/3eLVLF919y9BI907IYU wxGIsrnXaBEaBYyOmNzsJoMDRSzgwqVy7Po1tjH8gHAYd9FqQFyKMir7zPQ1U6Ki weZM3hBlZZ3XEE6bXBFbAa1ZZO7mjTlEn94IliUpta0qTEMR7wcgmm3tXOAdVHTe mvV1/6zeU1Ba+A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=vSeoIWMX5W2748vJK/OHR5PP8Irf4 5HCcLmaRrfN1L8=; b=ssagXgpIICeW366Zt9+CqgXFxBK8i7B8c2WVBpOo5odql ESX9lF08fVUeBiTQSQPX1oWGvmgSfZxP+iLjojuRlROEMS4qnHBgjtIEPiUQbEQI GXlzbdtwMaiaxwAMAoTVAzYB8jHAVHXkr4eVGabvJyNEkrS99kzU8eoPIiYwHS5S WSDrYdKXQdR/Nn8R95B+2HAnyzJw1xfjjgg1fmA4VDl61PtLvP3cZEffwqnTSC1j flYcXxNnaf31bAPf2Y4+F1j3z+v4etijHHUO0f8WxQRJSr+65bLs/PZ5BwKaCh+f w+5uiM56BEY4qtzHFjzy1uGZbArYUB0TEE2VhDoQA==
X-ME-Sender: <xms:Q-4qXvvLF7iod_uVfzW1JIa8P2fsbvwg3V1e1sl5s-7eRb-3Ie6NLQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrvdeggdeglecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesrgdtreerre ertdenucfhrhhomhepfdforghtthcujfhoghgrnhdfuceomhgrthhtsehmthhthhhgnhdr tghomheqnecuffhomhgrihhnpegvgigrmhhplhgvuddrtghomhdphhhtthhpshgtrhgrmh hrfhgtjeektdegvgigrghmphhlvgdvrdgtohhmnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepmhgrthhtsehmthhthhhgnhdrtghomh
X-ME-Proxy: <xmx:Q-4qXsxIdDofmyBPSXBoNMiw5YL5hyeYOhU6iTEMPsOykKsiedHHww> <xmx:Q-4qXlhQ-W9OY0rk9FQunSD_y7LAss8PVRTPznlGLX8g9diuseGiiw> <xmx:Q-4qXgDlCeWaVRSwmHkJlCdfTm2fpFbHzchgEmYbYnpAYfYcZg55sg> <xmx:Q-4qXp5DJK8kXprdGXBawHlfK33W1wlapT9ajXeHM0euvk2yGIyJCQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 51A34C200A4; Fri, 24 Jan 2020 08:16:51 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-777-gdb93371-fmstable-20200123v1
Mime-Version: 1.0
Message-Id: <3cd1b3b0-4dd1-4f35-8565-b91a4269bcb8@www.fastmail.com>
Date: Fri, 24 Jan 2020 07:16:31 -0600
From: Matt Hogan <matt@mtthgn.com>
To: jmap@ietf.org
Content-Type: multipart/alternative; boundary="be2e147c1aa7415baa084610dd1130e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/CLHZr8oTaUBm0gnHjvysxL8JdyY>
Subject: [Jmap] Question about authentication discovery
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2020 13:16:54 -0000
Hi everyone, I've been following along with the JMAP RFC for a while now, and I'm really excited about it! I have a question about authentication, specifically around how a JMAP client would know which authentication strategy to use for a given domain. Imagine the following JMAP servers: * example1.com, authenticates via HTTP SCRAM (RFC 7804) * example2.com, authenticates via HOBA( RFC 7486) If I want a JMAP client to work with any JMAP server, the client will need to know the form of authentication *before* it can successfully request a session. Are there currently any mechanisms for a client to discover this information, similar to how it can discover the URI for the session endpoint? Is the expectation that a user will have to specify to the client the authentication method and authentication URI? -- Matt
- [Jmap] Question about authentication discovery Matt Hogan
- Re: [Jmap] Question about authentication discovery Neil Jenkins