Messages - 2.4 Maybe better to write down the scope values to request object mapping
Issue #710
resolved
profile etc. are shorthand for the set of claims in the JSON within the request object.
Perhaps it may be a good idea to show the mapping. e.g.,
"openid profile" maps to
{
"userinfo":
{
"claims":
{
"name": null,
"family_name": null,
"given_name": null,
"middle_name": null,
"nickname": null,
"preferred_username":null,
"profile": null,
"picture": null,
"website":null,
"gender":null,
"birthdate":null,
"zoneinfo":null,
"locale":null,
"updated_time":null
}
},
"id_token":
{
}
}
Comments (4)
-
-
- changed milestone to Implementor's Draft
-
assigned issue to
Let's do this, but omit the empty id_token clause.
-
reporter - changed milestone to Implementer's Draft
-
- changed status to resolved
Fixed
#710- Gave an example of how requesting Claims with scope values is equivalent to requesting them with the "claims" request parameter. Added the "claims_parameter_supported" discovery parameter.→ <<cset 9cd555494adc>>
- Log in to comment
those are just the "default" claims for profile, as I read the text in the spec