Is Userinfo endpoint required?

[Mark Haine]

No description provided.

[Mark Haine]

Mark & Tony will collaborate on writing the necessary change

[Mark Haine]

There is a need for some implementations to only support delivery of claims via either id_token or userinfo endpoint.

It is unclear in OpenID Connect core whether that is permitted and there is no OP metadata support for expressing that.

There needs to be some work done to look at how this area could be more clearly defined both in the spec and in the OP metadata

[Mark Haine]

Propose new erata to Final: OpenID Connect Core 1.0 incorporating errata set 1

‌ Section 5.5

‌ “When the claims parameter is supported one or more of the available top-level members must be present”

‌ The claims_responses_supported Discovery result indicates which of the top-level members of the claims request the OP supports.

‌

Propose new erata to Final: OpenID Connect Discovery 1.0 incorporating errata set 1

‌ to section 3

‌ Add new metadata definition: 

claims_responses_supported: "OPTIONAL. A JSON array indicating the top-level members of the Claims request JSON object that are supported. Only valid when the “claims_parameter_supported” is present and true.

‌

[Mark Haine]

I raised two issues on OpenID AB/Connect WG to replace this

https://bitbucket.org/openid/connect/issues/1227/core-55-claims-parameter-requirements

https://bitbucket.org/openid/connect/issues/1228/discovery-3-new-metadata-item-for-claims

[Mark Haine]

Raised with AB/Connect Working Group for resolution