Re: [OAUTH-WG] OAuth 2.0 Authorization Server Metadata is now RFC 8414
Samuel Erdtman <samuel@erdtman.se> Fri, 29 June 2018 04:50 UTC
Return-Path: <samuel@erdtman.se>
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 49B66130E64 for <oauth@ietfa.amsl.com>; Thu, 28 Jun 2018 21:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=erdtman-se.20150623.gappssmtp.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 8nL9CLdNq6Bq for <oauth@ietfa.amsl.com>; Thu, 28 Jun 2018 21:50:42 -0700 (PDT)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (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 05376129C6A for <oauth@ietf.org>; Thu, 28 Jun 2018 21:50:41 -0700 (PDT)
Received: by mail-pf0-x241.google.com with SMTP id u16-v6so3635938pfh.3 for <oauth@ietf.org>; Thu, 28 Jun 2018 21:50:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erdtman-se.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QslFIOb8JYAFME4TPnS9shX8DTrXCMdJCdI8ihk6/bE=; b=dT2vouA8IYvV/1LdVuo83jHSFnXcP9dYb9o4kkYLEt+N3ypwLbOr79uiYpVGpZiznD kj4+6Qk+Nq56Sqv18WrOWYKtFQ9q19IU3HebvQjWeJfNZnRt6rD7vQIp28fpH9yH1JwK zxVA0Od+cJlHGyg8lGDtQ4cms9I8shXH+auD8AjHLLeej3qyxxl6mzj3r5E3v5OqUiBE dIWVhYFPMUq0GiOnWVAEFDSNpBB+DnOXUa5kwdviexe0P8olgTxe9/tEsfJtBNlS8TKY jh0lW5vNWoDfxsLTT+THGxeqOrGhN0cl4PVA71rD2wuYXtp+3jEDyHU2+UQxDa6YUc+I qSvw==
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=QslFIOb8JYAFME4TPnS9shX8DTrXCMdJCdI8ihk6/bE=; b=Nd3LRALx1US0DeLQhsc1b0t2w5qPcKQAPg9KpS4ZQBzBKbH7NLjSPDqiqbfGWedRey 1ieJ4g6L2HP/oWFI3HVGWA9oJQiWCnEVwqJIM3AtYklt0+Au14RDu6/pLlmqg3R6xWMn us0IFTnxw1iWsU8xP0OjD30ylD9ugJCSRPosRII7NeuZ2Lnf1zPz4VNKTziuYJ+jFk+Q 8ZrL0BVb1lo4cdPjDcggbbwnJqq+FSNZXGPQWfFQF/kMYskH3xXJpBxjDpWjxc9D8I8X h+ah4+UrKQhjMJe7tTvzrkNNF68UTSLby6yEWJJ4zdRWYVS6mALNHwfHpSx61E7hz5mh XLsw==
X-Gm-Message-State: APt69E3LO45O8HBMyn0NBvz0NtGT2KTDP7yzEJU5NgzvO20Kj4zD27dQ KDaHHxHPn+qoXHKXB9mVNipxDVSNvFLrg68nmAy5mQ==
X-Google-Smtp-Source: AAOMgpcEr6sz3ZHw/BoyvIJR/Z4xVK9oLUy6IozGY0ZSaAvqHF5o6MdHRKiWx9jk7knwSChN2OEAz8uaI/ybD4yoC2s=
X-Received: by 2002:a62:40dc:: with SMTP id f89-v6mr12789300pfd.194.1530247840636; Thu, 28 Jun 2018 21:50:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:d598:0:0:0:0 with HTTP; Thu, 28 Jun 2018 21:50:40 -0700 (PDT)
In-Reply-To: <A2992F1A-3405-4335-9FB0-9435495FDA88@tomitribe.com>
References: <BL0PR00MB0292114ED161717408E72C46F54F0@BL0PR00MB0292.namprd00.prod.outlook.com> <A2992F1A-3405-4335-9FB0-9435495FDA88@tomitribe.com>
From: Samuel Erdtman <samuel@erdtman.se>
Date: Fri, 29 Jun 2018 06:50:40 +0200
Message-ID: <CAF2hCbbvqxAz_fhnWMKPRAQBx56pfRzMBrtb1CXKt64LZa1oiA@mail.gmail.com>
To: David Blevins <dblevins@tomitribe.com>
Cc: Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f5b3c6056fc09616"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/TjzQXMVDlP4SuaqdF6C4YHFLpKk>
Subject: Re: [OAUTH-WG] OAuth 2.0 Authorization Server Metadata is now RFC 8414
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.26
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: Fri, 29 Jun 2018 04:50:46 -0000
Well done! On Fri, Jun 29, 2018 at 2:12 AM, David Blevins <dblevins@tomitribe.com> wrote: > I'm a new face, but did want to say congratulations to all. It's great to > see this movement into the OAuth 2.0 umbrella. > > > -- > David Blevins > http://twitter.com/dblevins > http://www.tomitribe.com > > On Jun 28, 2018, at 3:54 PM, Mike Jones <Michael.Jones=40microsoft. > com@dmarc.ietf.org> wrote: > > The OAuth 2.0 Authorization Server Metadata specification is now RFC 8414 > <https://www.rfc-editor.org/rfc/rfc8414.txt>. The abstract describes the > specification as: > > This specification defines a metadata format that an OAuth 2.0 client can > use to obtain the information needed to interact with an OAuth 2.0 > authorization server, including its endpoint locations and authorization > server capabilities. > > The specification defines a JSON metadata representation for OAuth 2.0 > authorization servers that is compatible with OpenID Connect Discovery 1.0 > <http://openid.net/specs/openid-connect-discovery-1_0.html>. This > specification is a true instance of standardizing existing practice. OAuth > 2.0 deployments have been using the OpenID Connect metadata format to > describe their endpoints and capabilities for years. This RFC makes this > existing practice a standard. > > Having a standard OAuth metadata format makes it easier for OAuth clients > to configure connections to OAuth authorization servers. See > https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml# > authorization-server-metadata > <https://www.iana.org/assignments/oauth-parameters/oauth-parameters..xhtml#authorization-server-metadata> > for the initial set of registered metadata values. > > Thanks to all of you who helped make this standard a reality! > > -- Mike > > P.S. This announcement was also posted at http://self-issued.info/?p=1883 > and as @selfissued <https://twitter.com/selfissued>. > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > >
- Re: [OAUTH-WG] OAuth 2.0 Authorization Server Met… David Blevins
- Re: [OAUTH-WG] OAuth 2.0 Authorization Server Met… Phil Hunt
- Re: [OAUTH-WG] OAuth 2.0 Authorization Server Met… Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth 2.0 Authorization Server Met… William Denniss
- [OAUTH-WG] OAuth 2.0 Authorization Server Metadat… Mike Jones
- Re: [OAUTH-WG] OAuth 2.0 Authorization Server Met… Samuel Erdtman