IETF Logo Mail Archive

Re: [OAUTH-WG] OAuth 2.0 Discovery Location

Thomas Broyer <t.broyer@gmail.com> Tue, 01 March 2016 09:24 UTC

Return-Path: <t.broyer@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC761B369D for <oauth@ietfa.amsl.com>; Tue, 1 Mar 2016 01:24:53 -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, SPF_PASS=-0.001] autolearn=ham
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 YYPNOpCLhtCt for <oauth@ietfa.amsl.com>; Tue, 1 Mar 2016 01:24:52 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (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 B49AC1B3696 for <oauth@ietf.org>; Tue, 1 Mar 2016 01:24:51 -0800 (PST)
Received: by mail-lb0-x22f.google.com with SMTP id bc4so95391705lbc.2 for <oauth@ietf.org>; Tue, 01 Mar 2016 01:24:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lHvdfISpfin0l+JXOM5osYLM+Ls745zP1AKP/Uaiyhk=; b=kQsir4jZVu77kKi9MWErZaFrSKKL9jRBXsRRQzcnBNfaGPOofA10arfT1ZB0EopsoC C7RF8jjuAqLF8johSoIzVn4im+ORkkuhFAkjNRVd2Yzg2uHswT9vOutusC8N4TzFTjQA LYradg/FtysqJ3gxYkS+Hmj2W7XF2gGI2PRSJ0kxU2OwLZrVlRtcQDzhWSxrCzAHbJMZ os3YGtxTB4K0YF2TM595nCYwHSsJL/iuTu6ngi+9Ge47p9shr1mMtNjqc40o8V0tlnhl +KmMkWIMnTLAf0uiUIMGQqruBMMbDWdyNGzGg20ejgw98SLb3uS/x36kTY14QvjGHoXZ 78rg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lHvdfISpfin0l+JXOM5osYLM+Ls745zP1AKP/Uaiyhk=; b=H0s+Glf08p+2GM7Y2G+zEQaCv3TWdvyl6ZFCqHCE1KEFqIAhnmKY+sHhwqGxO8b0P2 oPqvDgHm30meSKMOiaCrlKLPyX2MqKSj5XwGIN31+LKcHU1uAZFhIZA4elQpsLrMNS4w J/h3p0VhRGfoTm58JNQVMd/sIRLfJO6/ykjGi32+xayqFC0D5Af6x0Pzkerxo9zIKhme c2XzcPJ69GJ5Fni1B6QdR/V46oGqR+JgVxn+uOsPsBJE+/smSyLWx+FvlqEtSLerthjR q3uAR4Qp7cLcT16LUJChkdPnV2Ji6BcXtlO6E5oK5fbljab2l0zYs7r9oe4zdIQ43+oG ftIA==
X-Gm-Message-State: AD7BkJJLy5ad28GtEl7GjkRjTDOhdaGazB4ddpx29tYYTKQCp6RU2DhxPXdxP8YHDdEtT2tfeJETmeWtq/xsLA==
X-Received: by 10.112.199.7 with SMTP id jg7mr5812126lbc.109.1456824289875; Tue, 01 Mar 2016 01:24:49 -0800 (PST)
MIME-Version: 1.0
References: <E3BDAD5F-6DE2-4FB9-AEC0-4EE2D2BF8AC8@mit.edu> <BY2PR03MB44220A3CDA0552D439C9A2AF5A50@BY2PR03MB442.namprd03.prod.outlook.com> <BN3PR0301MB1234658E888AC37750E18D4EA6A50@BN3PR0301MB1234.namprd03.prod.outlook.com> <BY2PR03MB44295F4948FB3ABEAFBA3D8F5A50@BY2PR03MB442.namprd03.prod.outlook.com> <BN3PR0301MB123439E7F8083A5C557EED28A6A50@BN3PR0301MB1234.namprd03.prod.outlook.com> <4724BFD4-B761-40DC-9535-A0968DEAFD66@oracle.com> <BY2PR03MB442E135F59374B40084665EF5A50@BY2PR03MB442.namprd03.prod.outlook.com> <17E6C845-D633-45F6-A123-515437583F02@oracle.com> <BY2PR03MB442BA8094FF4718BCA93112F5A50@BY2PR03MB442.namprd03.prod.outlook.com> <BY2PR03MB442C4E813E7ADFED795526BF5A50@BY2PR03MB442.namprd03.prod.outlook.com> <53B19A70-3F17-423F-AE5E-DC6181B8FED7@oracle.com> <BY2PR03MB442847F4E292B4AA0498F52F5A60@BY2PR03MB442.namprd03.prod.outlook.com> <E7CF381C-5780-415C-8182-714B43F149CA@oracle.com> <56CEC24C.8040709@connect2id.com> <BY2PR03MB4425461F4C68FAAABC422BDF5A60@BY2PR03MB442.namprd03.prod.outlook.com> <CAF2hCbaowJs+aBU_RrQVj3R6RGX89nsUqinSgAevQeu2+=PS1A@mail.gmail.com> <BY2PR03MB442FFEDAA5B8ED7A8FAAD9BF5B80@BY2PR03MB442.namprd03.prod.outlook.com> <CA+k3eCTg_ztKj4z7y3JpUMF6Mt9PQdHjUw1J0_Rg4tVS=dsP6A@mail.gmail.com>
In-Reply-To: <CA+k3eCTg_ztKj4z7y3JpUMF6Mt9PQdHjUw1J0_Rg4tVS=dsP6A@mail.gmail.com>
From: Thomas Broyer <t.broyer@gmail.com>
Date: Tue, 01 Mar 2016 09:24:39 +0000
Message-ID: <CAEayHEOZTbOWTBaA-sj9s6jnsktFiacrfSEcMoLrqiwska0PQw@mail.gmail.com>
To: Brian Campbell <bcampbell@pingidentity.com>, Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary="001a11c259a44c5ea9052cf95646"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/47C5B4lMpeX4IPUZHB-9KSO8PHs>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth 2.0 Discovery Location
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Mar 2016 09:24:53 -0000

On Mon, Feb 29, 2016 at 11:35 PM Brian Campbell <bcampbell@pingidentity.com>
wrote:

> +1 for "OAuth 2.0 Authorization Server Discovery” from those two options.
>
> But what about "OAuth 2.0 Authorization Server Metadata”?
>
> The document in its current scope (which I agree with, BTW) isn't really
> about discovery so much as about describing the metadata at some
> well-known(ish) resource.
>

+1

(in case that wasn't obvious already by my previous mails)

v2.23.0 | Report a Bug | By Email