Re: [OAUTH-WG] OAuth Discovery spec pared down to its essence

Mike Jones <> Thu, 18 February 2016 19:36 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D13B91A1A76 for <>; Thu, 18 Feb 2016 11:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uEyuTXM8cuQY for <>; Thu, 18 Feb 2016 11:36:42 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 813DB1A0370 for <>; Thu, 18 Feb 2016 11:36:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=hIPKCctkeRofvQpuOiuD3CIkUhwu5OwCkdAtdAmlU9Q=; b=cHOPQAQ4wWHzGVeWWelRFlQHhX7iTcaJxh06kbO3xV0uSGBzkLWruPYIWe86PhUH5bIS2NlFGPlf1KSxzrOg27ecIQGymLNQuyC25sOe0xJ4OutOPwlz+kdBeC3gz+VTg823fX4BHk57GkPYodwzoxq4x79r1mEbDT/TZmKgT0k=
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.409.15; Thu, 18 Feb 2016 19:36:40 +0000
Received: from ([]) by ([]) with mapi id 15.01.0409.017; Thu, 18 Feb 2016 19:36:40 +0000
From: Mike Jones <>
To: William Denniss <>
Thread-Topic: [OAUTH-WG] OAuth Discovery spec pared down to its essence
Date: Thu, 18 Feb 2016 19:36:40 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
x-originating-ip: []
x-ms-office365-filtering-correlation-id: 5db11465-6b05-441e-9950-08d3389ad31c
x-microsoft-exchange-diagnostics: 1; BY1PR0301MB1237; 5:6WvRZuN69BRs3uWUBrtbvHAkzeGRNiiKEnVah5ppJxiEPJIUJ+jao03PGdHxxhWB51qhn7XUcb2vcb1k4QXde/Smuqm1kKeVEyRg21tJ4ztnXnTFo18EqxU7BicXt3VaMENZCLXp+/AyoA7IG2FcJw==; 24:RqPZ8pDKy59h+a8iaifr8AMFDgjybMU7Loe4xcjGFiO7Lrc0fEDHoz+8B3LqigVDEE/4JJyGw2WOHjfyGj/9GW/DsCc5U/ypzCqdEosRxUY=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0301MB1237;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(61426038)(61427038); SRVR:BY1PR0301MB1237; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0301MB1237;
x-forefront-prvs: 085634EFF4
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(164054003)(24454002)(57704003)(479174004)(377454003)(13464003)(6116002)(5004730100002)(86612001)(93886004)(5005710100001)(87936001)(66066001)(3846002)(102836003)(86362001)(19300405004)(16236675004)(790700001)(5001960100002)(19617315012)(10400500002)(10290500002)(74316001)(586003)(5008740100001)(19580405001)(77096005)(19625215002)(15975445007)(2906002)(40100003)(19580395003)(3660700001)(3900700001)(76576001)(33656002)(3280700002)(5003600100002)(10090500001)(4326007)(2950100001)(50986999)(110136002)(11100500001)(76176999)(1220700001)(1096002)(5002640100001)(99286002)(189998001)(92566002)(54356999)(122556002)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0301MB1237;; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/alternative; boundary="_000_BY2PR03MB442A29EEEFDF8951EF7A8C5F5AF0BY2PR03MB442namprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2016 19:36:40.5013 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0301MB1237
Archived-At: <>
Cc: "" <>
Subject: Re: [OAUTH-WG] OAuth Discovery spec pared down to its essence
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 18 Feb 2016 19:36:51 -0000

Thanks, William.  I’m good with referencing the registry in Section 2.  I’ll think about the registered/public/private comment.

It’s fine to reference oauth-mix-up-mitigation as a draft in a finished RFC as long as it’s an informative and not a normative reference.

                                                          -- Mike

From: William Denniss []
Sent: Thursday, February 18, 2016 11:28 AM
To: Mike Jones <>
Cc: John Bradley <>; Anthony Nadalin <>;
Subject: Re: [OAUTH-WG] OAuth Discovery spec pared down to its essence

Two review comments:

Can the text in "Section 2.  Authorization Server Metadata" near the end regarding additional metadata be expanded? I think we should reference the IANA registry established by this spec in that section (as this will be the reference point for people looking for other registered metadata), and possibly mention something about registered vs unregistered parameters and interoperability. At present if you only read that section it is a little vague.

I like the treatment of claims in the JWT spec, splitting into 3 groups: registered, public and private. Not saying we should mirror it exactly, but as an implementer I liked how clearly it was stated in that spec.

Since this doc is in WG Last call, do we need to remove the reference to the mix-up I-D (Section 2, "issuer"), or are we expecting them to be finalized together?

On Thu, Feb 18, 2016 at 10:42 AM, Mike Jones <<>> wrote:
I'm fine with changing dynamic registration from being RECOMMENDED to OPTIONAL.  That's good actionable feedback.  Likewise, looking at again, we also need to change jwks_uri from REQUIRED to OPTIONAL, since not all OAuth deployments need keys.

I expect more good, actionable feedback to also come from the WGLC as people carefully read the draft with fresh eyes.

                                -- Mike

-----Original Message-----
From: John Bradley [<>]
Sent: Thursday, February 18, 2016 10:33 AM
To: Anthony Nadalin <<>>
Cc: Mike Jones <<>>; Hannes Tschofenig <<>>; Phil Hunt <<>>;<>
Subject: Re: [OAUTH-WG] OAuth Discovery spec pared down to its essence

We are establishing a registry.  Some folks do use dynamic client registration.

We can register it in this document or take it out and let others register it once the registry is established.

It will be registered one way or the other.

One of the reasons for starting last call is to get people to read the draft and comment.
That seems to be working.

If you have specific security considerations, please let us know so they can be addressed.   Text is always appreciated.

John B.

> On Feb 18, 2016, at 1:27 PM, Anthony Nadalin <<>> wrote:
> Not sure about that. There are things that are "recommended" like the dynamic registration endpoint, I don't understand why this is recommended as a lot of folks still don't do this. There are security considerations about all the information that is in the discovery that have not been addressed.
> -----Original Message-----
> From: Mike Jones
> Sent: Thursday, February 18, 2016 10:18 AM
> To: Anthony Nadalin <<>>; Hannes Tschofenig <<>>; Phil Hunt <<>>; John Bradley <<>>
> Cc:<>
> Subject: RE: [OAUTH-WG] OAuth Discovery spec pared down to its essence
> It's the OAuth-specific subset of what's already widely deployed.  Nothing was invented - just subsetted.
> I think it's already as simple as possible unless the working group decides to remove even more functionality (which it can obviously do).
>                               -- Mike
> -----Original Message-----
> From: OAuth [<>] On Behalf Of Anthony Nadalin
> Sent: Thursday, February 18, 2016 10:13 AM
> To: Hannes Tschofenig <<>>; Phil Hunt <<>>; John Bradley <<>>
> Cc:<>
> Subject: Re: [OAUTH-WG] OAuth Discovery spec pared down to its essence
> I also think we are way far from last call (and surprised to see last call issued) on this document as it is still very complex for something that should be very simple
> -----Original Message-----
> From: OAuth [<>] On Behalf Of Hannes Tschofenig
> Sent: Thursday, February 18, 2016 6:47 AM
> To: Phil Hunt <<>>; John Bradley <<>>
> Cc:<>
> Subject: Re: [OAUTH-WG] OAuth Discovery spec pared down to its essence
> On 02/18/2016 03:06 PM, Phil Hunt wrote:
>> BTW. I think we are FAR from Last Call on this topic.
> Thanks for your feedback, Phil. As you have seen I had issued a WGLC prior to your message based on the claim from the authors that they believe the document is finished.
> We will, of course, take all reviews into account and see where we are with the discovery spec. I, as the shepherd, will also do my review and I encourage many working group members to also take a look at the document and to provide their input.
> Ciao
> Hannes
> _______________________________________________
> OAuth mailing list

OAuth mailing list<>