[Openid-specs-ab] OpenID Connect Federation Draft 18 Published

[Mike Jones]

Having consulted with Roland Hedberg (in person!), we decided to publish the current editor's draft of the OpenID Connect Federation specification as draft 18.  This contains substantial enhancements since the previous draft from September 2021.  Changes recorded in the history entry<https://openid.net/specs/openid-connect-federation-1_0.html#rfc.appendix.E> are:
-18
*        Moved from a federation API to separate endpoints per operation.
*        Added descriptions of the list, resolve and status federation endpoints.
*        Registered the client_registration_types_supported and federation_registration_endpoint authorization server metadata parameters.
*        Registered the client_registration_type dynamic client registration parameter.
*        Registered and used the application/entity-statement+jwt media type.
*        Registered the application/trust-mark+jwt media type.
*        Trust marks: the claim mark has been renamed to logo_uri.
*        New federation endpoint: Resolve Entity Statement.
*        New federation endpoint: Trust Mark Status.
*        Federation API, Fetch: iss parameter is optional.
*        Trust Marks: added non normative examples.
*        expanded section 8.1: included entity configurations.
*        Fixed #1373 - More clearly defined the term Entity Statement, both in the Terminology section and in the Entity Statement section.
There are currently eight Federation open issues<https://bitbucket.org/openid/connect/issues?status=new&status=open&component=Federation> in the issue tracker.  Please review them and add your thoughts.

                                                       Thanks,
                                                       -- Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20220505/c548b714/attachment.html>