Re: [OAUTH-WG] Direct Grant missing in draft-parecki-oauth-v2-1
Francis Pouatcha <fpo@adorsys.de> Thu, 09 April 2020 17:07 UTC
Return-Path: <fpo@adorsys.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 720113A0CD3 for <oauth@ietfa.amsl.com>; Thu, 9 Apr 2020 10:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, 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=adorsys.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 NQyB8tQ2t-_w for <oauth@ietfa.amsl.com>; Thu, 9 Apr 2020 10:07:14 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 BEF113A0CCE for <oauth@ietf.org>; Thu, 9 Apr 2020 10:07:14 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id s13so189172lfb.9 for <oauth@ietf.org>; Thu, 09 Apr 2020 10:07:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adorsys.de; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LWKoP9davg3zptAp54o1xhv81QoYrPZgC/4I16NbNHM=; b=LvaWOhYPdBsLsH8N8JXAE60hlZe3+rXGB5hBvwh530eYcFRizvuU0IMCuE5T2JEXs7 axyeZi2mEtzbQYPUeUgm7cs7n0E1tuorcqxkjt6enA+AuECqeOUY3jVi32ZrfclnPTZx +NvXpYVPomTQX6VLtWhYU2eyMxqVaze267No0=
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=LWKoP9davg3zptAp54o1xhv81QoYrPZgC/4I16NbNHM=; b=HWYyF6terjjSskoDrKTh9P/YdFNcc/L8TRgU38VK9WYVd45dzpLXZsAp2bEi3T4HMJ h7WP6A9OV5JQb/l7eXCB2KaT1Uno4qSa2RV9Oox0Mr8Oek7QRiP9FUHpPET3cEt8HPvD QVY62XRRwNexvRJCixVuyvH287MnlZt6sWPcacfstfyLPrm8yxke17oDeGRz1aice5YY xqljylhwVN/pTngD/zU//L4PEgVMXZLZa2zDw15lFuhAF1ydlQ+eZUy8YU18xwAlAdnG vJ1LT9yEV8wT58UPQOyb5vOFGu4aodQmEr1bUcWQGU+kDdSo59miRQSn6azaG/6O+dlr BKRQ==
X-Gm-Message-State: AGi0PubqDMKX/jngaw5xYsT3LH4q92ScQ9tWnaVf/0BbUiiMAQeim/X1 p/tTi4W5AXLBad5mVsNUiWGXPxcRDthlrX9ArmA2I9XSR58=
X-Google-Smtp-Source: APiQypI3R/ey8VMxWKIXv667rUtzb5ztwsFWvqN96Ka0YDhF8dZZVz3LEG1VWbFkvAMNG/NiT1UgH6WhT7b4WX0C/cs=
X-Received: by 2002:a05:6512:308e:: with SMTP id z14mr182917lfd.110.1586452032396; Thu, 09 Apr 2020 10:07:12 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.1071.1586449554.10597.oauth@ietf.org>
In-Reply-To: <mailman.1071.1586449554.10597.oauth@ietf.org>
From: Francis Pouatcha <fpo@adorsys.de>
Date: Thu, 09 Apr 2020 13:07:01 -0400
Message-ID: <CAOW4vyPvKytC8wOAizgFuHYYs7wcp51oo-u67WdHYGU1+zEASw@mail.gmail.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d83b9505a2dea5be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/fzmHMpflrcpq_zyiysylsrWxpMM>
Subject: Re: [OAUTH-WG] Direct Grant missing in draft-parecki-oauth-v2-1
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, 09 Apr 2020 17:07:17 -0000
> > > Am 09.04.20 um 09:55 schrieb Rob Otto: > > I'd imagine you have to pre-register each client and then use HOTP or > > TOTP to generate one-time passcodes.? > > > > I can come up with a couple of other ways as well, but I'm interested to > hear what Francis sees "in the wild". There are many ways of implementing "Direct Grant". We shall distinguish between approaches which reuse the ROPC-Flow as is, and those which require an extension of the ROPC-Flow (e.g. with initialization steps which return challenges). For a customer project we had it simply done with a TOPT without extension of the ROPC grant oAuth2.0. We extended AS to check {username, TOTP} instead of a permanent password. -> The login page embedded in the RP user agent displays a form requesting {username, TOTP} -> For registration and OTP setup we display a link to the AS (no redirect). -> Main purpose was mitigating hazard associated with user agent redirect. -> FreeOTP is the reference APP for OTP. Remember my initial message requested an alternative "DIRECT GRANT" flow (means WITHOUT REDIRECT). BTW: I went through Dick's reference https://mailarchive.ietf.org/arch/msg/oauth/mG6tkmXSOxwakC0184snKCGxfSE/. We might want to continue there or stay here if the foccuss shifts away of oAuth2.1.
- [OAUTH-WG] Direct Grant missing in draft-parecki-… Francis Pouatcha
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Aaron Parecki
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Francis Pouatcha
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Dick Hardt
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Daniel Fett
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Rob Otto
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Daniel Fett
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Justin Richer
- Re: [OAUTH-WG] Direct Grant missing in draft-pare… Francis Pouatcha