[Openid-specs-ab] Issue #1504: There are Open Issues listed in the spec that we don't plan to address (openid/connect)

mbj issues-reply at bitbucket.org
Tue May 24 15:27:57 UTC 2022


New issue 1504: There are Open Issues listed in the spec that we don't plan to address
https://bitbucket.org/openid/connect/issues/1504/there-are-open-issues-listed-in-the-spec

Michael Jones:

There’s currently a set of Open Issues listed in the spec at [https://openid.net/specs/openid-connect-federation-1\_0-19.html#rfc.appendix.D](https://openid.net/specs/openid-connect-federation-1_0-19.html#rfc.appendix.D).  To finish, we need to address them and/or determine that we do not plan to address some of them.  Based on discussions with Roland and Giuseppe, I propose that not do further work to address these:

* The representation for RPs that are native applications needs to be defined.
* A mechanism MAY be needed for bounding key lifetimes.
* SAML2 as used in Research and Education federations uses post-/prefix matching on metadata in some cases. We might need something similar or just use regular expressions.
* Add a diagram showing the relationships between FOs, orgs, sub-orgs, and leaf entities.

For the last point, Giuseppe points that we already have the diagram at [https://openid.net/specs/openid-connect-federation-1\_0-19.html#rfc.appendix.A](https://openid.net/specs/openid-connect-federation-1_0-19.html#rfc.appendix.A).

Responsible: Michael Jones




More information about the Openid-specs-ab mailing list