IETF Logo Mail Archive

Re: [OAUTH-WG] OAuth 2.0 Pushed Authorization Requests: Implementation Status

Daniel Fett <fett@danielfett.de> Thu, 25 March 2021 10:55 UTC

Return-Path: <fett@danielfett.de>
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 CCF2D3A1CF8 for <oauth@ietfa.amsl.com>; Thu, 25 Mar 2021 03:55:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=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=danielfett.de
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 OYcr__SqC-Q8 for <oauth@ietfa.amsl.com>; Thu, 25 Mar 2021 03:55:17 -0700 (PDT)
Received: from d3f.me (redstone.d3f.me [5.9.29.41]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 480A93A1D8D for <oauth@ietf.org>; Thu, 25 Mar 2021 03:54:52 -0700 (PDT)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by d3f.me (Postfix) with ESMTPA id 5199D22424 for <oauth@ietf.org>; Thu, 25 Mar 2021 10:54:50 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=dkim; t=1616669690; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7Rp6ArWnvwZgQMnprLQuS4Kuq+xrjPg9yi77AE3h7X8=; b=a5VPQNMTvdW5BPEDXAaFhTaZXQ/A+wSjlFqR08CzrZF0XEi6K3tDpzZCieEeV+u1UOJ+JY h1fM+EfgHylY0YTQEhAeK6khVL03U5CtFX63AqRlhaaeX2SM5AB5FU9WT7p8SJiVEuNbSA XArdMcWayG9EMZroUkp8ZWVzwbJ69sM=
To: oauth@ietf.org
References: <VI1PR08MB2639645D092026CCD11A2328FA639@VI1PR08MB2639.eurprd08.prod.outlook.com>
From: Daniel Fett <fett@danielfett.de>
Message-ID: <7bc4c2ba-3101-f730-8fd4-7b8154979c29@danielfett.de>
Date: Thu, 25 Mar 2021 11:54:49 +0100
MIME-Version: 1.0
In-Reply-To: <VI1PR08MB2639645D092026CCD11A2328FA639@VI1PR08MB2639.eurprd08.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------980E73A7BC9CE4139B0AAFFC"
Content-Language: de-DE
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=dkim; t=1616669690; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7Rp6ArWnvwZgQMnprLQuS4Kuq+xrjPg9yi77AE3h7X8=; b=DM2Lvm17XZ3jW2N2so4H377LyoQZ8CEXGYARL9Xy1eyvbd5O6+urwlyMlA0j3fa1C4kh34 uKW/IzkfzjduJ9HzzF+JeRwVCFiMys+PX5rWMo+k7ab4gS+Wi+CdWuBqam7+Oq5m+e84I6 VCe6IP6cTICusUgceuBhMo1dOzNWAWo=
ARC-Seal: i=1; s=dkim; d=danielfett.de; t=1616669690; a=rsa-sha256; cv=none; b=JKnEzkAjKZXXf7GhdqKblwnGiTR0Y3H8OrA2K8hsjPM/9Ea42pIrhLe4vCT+R8DM0tEI22 JACP7m0HjS5Ht7GKK7+iQfWpPhGMQyMMNtVwO2nl5BULZz8ESxfOXu7LmsOeN6Q6MLGcU1 O8CMzdMDVPU3Md+tK2OXI1bxbbQkOko=
ARC-Authentication-Results: i=1; d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
Authentication-Results: d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
X-Spamd-Bar: --
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/F7SJv1NIHs7Hx6_9RBUuTnmMX_Y>
Subject: Re: [OAUTH-WG] OAuth 2.0 Pushed Authorization Requests: Implementation Status
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: Thu, 25 Mar 2021 10:55:23 -0000

Hi Hannes,

as mentioned by Brian, the yes Signing Flow is based on PAR and
therefore implemented by our banks (> 1000).

A python client for the yes signing flow is publicly available that uses
PAR: https://github.com/yescom/pyyes

-Daniel


Am 24.03.21 um 20:53 schrieb Hannes Tschofenig:
>
> Hi all,
>
>  
>
> I am working on the shepherd writeup and I need information about the
> implementation status of this specification.
>
>  
>
> Can you share whether you are implementing, or planning to implement
> this specification? If there is open source, please drop a link to the
> mailing list. If you implement it in your product, please let us know
> as well.  
>
>  
>
> This information helps the steering committee to judge the quality and
> maturity of the work.
>
>  
>
> Ciao
>
> Hannes
>
>  
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose
> the contents to any other person, use it for any purpose, or store or
> copy the information in any medium. Thank you.
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth


-- 
https://danielfett.de

v2.23.0 | Report a Bug | By Email