IETF Logo Mail Archive

[httpapi] Fwd: New Version Notification for draft-schwartz-httpapi-popup-authentication-00.txt

Ben Schwartz <bemasc@google.com> Mon, 17 October 2022 18:52 UTC

Return-Path: <bemasc@google.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0733BC1524DA for <httpapi@ietfa.amsl.com>; Mon, 17 Oct 2022 11:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.607
X-Spam-Level:
X-Spam-Status: No, score=-17.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 CqAA66C58SpF for <httpapi@ietfa.amsl.com>; Mon, 17 Oct 2022 11:52:25 -0700 (PDT)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 42304C1524A1 for <httpapi@ietf.org>; Mon, 17 Oct 2022 11:52:25 -0700 (PDT)
Received: by mail-vs1-xe31.google.com with SMTP id 63so12453127vse.2 for <httpapi@ietf.org>; Mon, 17 Oct 2022 11:52:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=3l9WciL0BvHHSyu20GU5vKx3tgUQyLQzTyS7wxTRMjM=; b=X4d/GP8UTzhpIiTBSBl1AOCFFpzwhRvdLi5ouyv8MThkQC9tfr3jgL6S2v2B7LckHH 9KhDBMTHEgnUftcAlQhkFF+Dk4v1vXXTeQNRDOS7DXENBKlQrJdsSN5Ks2bm7MazMyM9 TiuKUjWnYcZzFeoY7SOYxuqyL+9M0sT3wP5Bm0XKNwhRzurPELetKkGejLjLuItC8rze jCALV7CzWK47I4T/xCaWLThN7KjWAIZbkNB9jffWoNZLgjCTuHjFWPOBuDkczntyecsX FStp8O0UcSLcvjVt3P6nrCzeWw+nax9YM3e1ZWO5jet8B7sPpQcjEGWMbBBX/zceCdh/ BrmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=3l9WciL0BvHHSyu20GU5vKx3tgUQyLQzTyS7wxTRMjM=; b=czejtCZkrEdaLc36dAaUMHlnPYqee2DERU3ofzlOaWIT1/NWw9rw0Owat3OZa0dyfD Xlf63nkIUp1/NOSwlXJGdryxxJCLwgWE/GHWQx62ZGy8JlAq0pKXgCoLKBY9DEpdVx/C bGUJxw2a8FXcacg9DEfor5RNRmqj7YQy/zQ5S9jYcOmdGVvRD983yiL8yFVxTE2evY46 t4dHrAjbWsNUdU6Dyk0o2Mcn4FkQmzXg6Ew4a/AZ6kFoqpfFW96SJbE8C6AenWPwB4h7 +XNM0bPfrTbHsN4CGFH7VogiBD1iQN0JFWGbbXJE96/SVdN2zSJPSyTWFHKXabGkR5aa jyfw==
X-Gm-Message-State: ACrzQf1WolO4YmnHSZgp//o+5q4Iih6Jcluq1fhAV0AuR4ZSrCq/aOZ7 4ImSHCox51Gv4e3lwyAU1KRNBsi9Ll3YO4VG2BTtGTGX9Pg=
X-Google-Smtp-Source: AMsMyM5OGJAP4XDu0VwkRZn7vcHC3ZmfrSOxZbFqzKeY+jsrMS9/lQnYDhZauF9UbMFthcwEBLJ+zZaFOxolkT5osk0=
X-Received: by 2002:a67:e1de:0:b0:3a6:f69b:b41a with SMTP id p30-20020a67e1de000000b003a6f69bb41amr5256305vsl.19.1666032743761; Mon, 17 Oct 2022 11:52:23 -0700 (PDT)
MIME-Version: 1.0
References: <166603213365.23795.4741558550670032108@ietfa.amsl.com>
In-Reply-To: <166603213365.23795.4741558550670032108@ietfa.amsl.com>
From: Ben Schwartz <bemasc@google.com>
Date: Mon, 17 Oct 2022 14:52:11 -0400
Message-ID: <CAHbrMsD3GBWAykHk0pf2gtJpVyu=vgJzi-Si4uK3OcMS0F_K4w@mail.gmail.com>
To: httpapi@ietf.org, oauth@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000e7586505eb3f795a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/sv4Ui21uumfY9jcZz5qCKid9vkc>
Subject: [httpapi] Fwd: New Version Notification for draft-schwartz-httpapi-popup-authentication-00.txt
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2022 18:52:29 -0000

Hi HTTPAPI and OAUTH,

This is a new draft that attempts to define a useful convention for HTTP
authentication: a way to tell the client to open a browser window to start
authentication, and to close that window when authentication is complete.

I think this might be a good fit for HTTPAPI, since it is really a building
block for other specifications, and it extends HTTP (by defining a new
WWW-Authentication "scheme").  However, I would also appreciate review from
OAuth experts, because I would like this design to work well with
server-to-server OAuth, and to match well with OAuth conventions if
possible.

I would like to present this idea at IETF 115.

--Ben

P.S. For background, this comes out of a conversation in MASQUE about how a
user-selected MASQUE proxy can trigger a modern login flow.

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Oct 17, 2022 at 2:42 PM
Subject: New Version Notification for
draft-schwartz-httpapi-popup-authentication-00.txt
To: Benjamin M. Schwartz <bemasc@google.com>



A new version of I-D, draft-schwartz-httpapi-popup-authentication-00.txt
has been successfully submitted by Benjamin Schwartz and posted to the
IETF repository.

Name:           draft-schwartz-httpapi-popup-authentication
Revision:       00
Title:          Interactive Authentication of Non-Interactive HTTP Requests
Document date:  2022-10-17
Group:          Individual Submission
Pages:          9
URL:
https://www.ietf.org/archive/id/draft-schwartz-httpapi-popup-authentication-00.txt
Status:
https://datatracker.ietf.org/doc/draft-schwartz-httpapi-popup-authentication/
Html:
https://www.ietf.org/archive/id/draft-schwartz-httpapi-popup-authentication-00.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-schwartz-httpapi-popup-authentication


Abstract:
   On the World Wide Web, a rich ecosystem of authentication options has
   been developed to support access control for HTTP resources.
   However, non-interactive usage of HTTP remains limited to the simple
   authentication mechanisms defined in the HTTP standards.  This
   specification allows non-interactive HTTP contexts to open a browser-
   like authentication context when necessary, and close it when
   authentication is complete.




The IETF Secretariat

v2.41.0 | Report a Bug | By Email | System Status