Re: [OAUTH-WG] Question on REQUIRED metadata in https://tools.ietf.org/html/draft-ietf-oauth-discovery-07
Dick Hardt <dick.hardt@gmail.com> Tue, 14 November 2017 10:12 UTC
Return-Path: <dick.hardt@gmail.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 DBA18126B6E for <oauth@ietfa.amsl.com>; Tue, 14 Nov 2017 02:12:49 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ul7ItEruiPiC for <oauth@ietfa.amsl.com>; Tue, 14 Nov 2017 02:12:48 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 4A4EB124B09 for <oauth@ietf.org>; Tue, 14 Nov 2017 02:12:48 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id i15so3753193pfa.3 for <oauth@ietf.org>; Tue, 14 Nov 2017 02:12:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rxGrOaS74Gt6IVZuo2kSpR21mYjFb4GrS5UFrdyRLTA=; b=hS+SjLpiEYF2V3lahk8HBNXSZECjHh3OuoofO17yn7k8Vstw0OeCQ55x4Xs0fyAjQJ qMcmJvEWbSF93b57lXwDV6Lq7ri9EnyLdYLVoy9xf+JtpOxYWQZnstNhNiGlot+ZKesX wesPJVwHXTEcM20WrlmR8/haddpSU8rLA2eYL7c/QK8QWJScqfNsK3CPeggdkvvM6BIF nimYB6xS9+89vLS9zfyzI/qyJMxeCifiDthemCnT6N3ao9zVzT/q9SGpYgKrAmdLmfaz w9bLZbQtcRd/uKdBsI9Q47IceEc5vSyfIMg044HktVxfY5u2o4SX4j3QARkkLr02cpIg dr2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rxGrOaS74Gt6IVZuo2kSpR21mYjFb4GrS5UFrdyRLTA=; b=O7nsmCq2SKkwzXy2G3+nXVB22Uw8jWJOuWzdlW9rH+GPGrP5eF3CQziAjMNQblaS26 csMxt36vXW+Dx+INXm/lyXy9Rahx6GmvaEaL4zW4Z7cRWCu4IA4qIbCt9IJCChfbiodj 8CzPEDun5A2hJbWOXP5YD25qD/652fttQEAqgK/TzsrW1QGTr/YHs8NEsK+Ik9cM44jc FAXSr60Wyl83AYHeUXHruIY8dS3FTx8DEujsEIeWLrkMLS2NMTEgywKVTArHGlSru01w 5+2fctg8MYZAZBGqLYUmUOI0e35pFcnIE1h0teh9p+DOrU4pwJFghWox4eWVwmQ0amfa rPTg==
X-Gm-Message-State: AJaThX7FYgITsDKCOHn0i6rkVkgiWLGxWDJ+6uUS21y3bKWVOqvceM3h RepIwcN/6uZZ+15Xxdg2u3C/sxBElS/BE7UAd9A=
X-Google-Smtp-Source: AGs4zMYdXcGPrJXhMFw9RF1zZq+aYaB3eR0BXTfBu49oJ2L+duOGsZ2WWDsaSN4dbEU1ExABlxnJHdpF2afGqx++bn0=
X-Received: by 10.98.117.137 with SMTP id q131mr5612603pfc.165.1510654367764; Tue, 14 Nov 2017 02:12:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.190.1 with HTTP; Tue, 14 Nov 2017 02:12:27 -0800 (PST)
In-Reply-To: <CY4PR21MB05044E0BFE6AE2B5CF88833BF5280@CY4PR21MB0504.namprd21.prod.outlook.com>
References: <CAD9ie-shUhkwf4zkmku9JdbQ7uzxWxcZXwe-mfD+evcvw-VBbA@mail.gmail.com> <CY4PR21MB05044E0BFE6AE2B5CF88833BF5280@CY4PR21MB0504.namprd21.prod.outlook.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Tue, 14 Nov 2017 18:12:27 +0800
Message-ID: <CAD9ie-scPCscKyMMNN3SDx9p91dvz2fV8QLQfNcbBrd9vSPO=w@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c04fe1ef81624055deea097"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Thu-BlqZe1gt_k-ZGZ2-AhKWJ9o>
Subject: Re: [OAUTH-WG] Question on REQUIRED metadata in https://tools.ietf.org/html/draft-ietf-oauth-discovery-07
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 14 Nov 2017 10:12:50 -0000
Thanks for the quick response Mike. Good to know I understand specs once in awhile. /Dick On Tue, Nov 14, 2017 at 5:14 PM, Mike Jones <Michael.Jones@microsoft.com> wrote: > Good catch. The authorization_endpoint should only be required if flows > are supported that need it. Our old favorite, the Resource Owner Password > Credentials flow doesn’t use it, correct? Likewise, the Client Credentials > flow doesn’t. I’ll plan to make appropriate updates in -08. > > > > -- Mike > > > > *From:* Dick Hardt [mailto:dick.hardt@gmail.com] > *Sent:* Tuesday, November 14, 2017 5:02 PM > *To:* oauth@ietf.org; Mike Jones <Michael.Jones@microsoft.com> > *Subject:* Question on REQUIRED metadata in https://tools.ietf.org/html/ > draft-ietf-oauth-discovery-07 > > > > I was reviewing https://tools.ietf.org/html/draft-ietf-oauth-discovery-07 > and noticed that in https://tools.ietf.org/html/draft-ietf-oauth- > discovery-07#section-2 that authorization_endpoint is REQUIRED. > > > > I am working on deployments that are two-legged OAuth where there is > no authorization_endpoint, but having a discovery document would be super > useful. > > > > Additionally, in https://tools.ietf.org/html/draft-hardt-oauth- > distributed-00, discovery would be useful, but there may not be > an authorization_endpoint may not be needed in the authorization server as > it is a two legged OAuth flow (ie, there is no user granting permission, > the client is requesting an access token to use at resources) > > > > Is there a reason why authorization_endpoint is REQUIRED? > > > > /Dick > > > -- Subscribe to the HARDTWARE <http://hardtware.com/> mail list to learn about projects I am working on!