- changed status to open
Agree on the Self-issued OpenID Connect Provider Requirements Document
Need to reach consensus on the Self-issued OpenID Connect Provider Requirements Document in the AB/C WG to move to the drafting stage.
Document: https://bitbucket.org/openid/connect/src/master/SIOP/siop-requirements.md
Comments (3)
-
-
reporter The rough consensus on the requirements have been reached during the call on Nov 16/17th.
To define the scope of initial v2 draft, five items have been highlighted from the requirements list (for details see “SIOP Scope proposal“ email thread):
- Enabling portable(domain-free) subject identifiers between providers - creation of subject identifiers that are not intrinsically bound to a particular OP
- Provider discovery and registration - how does an RP come to have a relationship with an OP or understand its capabilities along with what role the user plays in this selection/discovery process.
- RP - OP co-location on the same device - Dealing with the unique requirements that are brought about when the OP the RP is communicating with is on the same device (e.g in the form of a PWA or Native App), rather than a traditional Authorization server.
- Credential Issuance support - Issuing credentials from OpenID Connect flows.
- Credential Presentation support - Presenting credentials in OpenID Connect flows.
On Dec 14th and 17th calls, rough agreement on scopes 1, 2, and 4 has been reached.
During the same call, additional clarification was made: key rotation is in scope, while specific key recovery mechanisms are not.
-
reporter - changed status to closed
closed per agreement on Nov 16/17th call. Discussion moved to the scopes discussion on the ML and the call.
- Log in to comment