Correct Data Language for Contact Details (profile scope and individual claims) #504
Labels
Consumer experience
Issues related to Consumer experience Standards.
Projects
Description
A documentation error was introduced in v1.15.0 of the standards when dealing with the OpenID Connect profile scope and OIDC standard claims. This has caused some confusion for participants implementing individual named claims and the profile scope. This change request seeks to address the documentation error to remove confusion with how ADRs request and DHs authorise individual contact detail claims.
These claims, if supported, must be requested individually and were not intended to be requested using the profile scope as a catch-all substitute. The description for the Contact Details data language incorrectly implies the profile scope can be used as a mechanism to request the standard OIDC contact detail claims as well as the name claims.
No future dated obligation would be provided because it clarifies the optional nature of the contact details claims. This change corrects the change raised in DP216 which has a July 1st 2022 obligation date for the introduction of Profile scope data language.
Area Affected
Data Language Standards: Profile scope.
Change Proposed
Change title from “Profile Scope” to “Profile Scope and OpenID Connect Standard Claims”
Change “Authorisation scopes” description for Contact Details to be “One or more of these standard OIDC claims:”
This drops the “OIDC Profile scope and/or” section and clarifies the claims are standard OIDC claims
Include a "Required" column to articulate which claims and scopes the Data Holders MUST support versus which individual OIDC claims are at the discretion of the Data Holder to support. This removes implementation ambiguity for Data Holders.
In table form, this would be represented as follows:
*See 5.4. Requesting Claims using Scope Values on the OIDC website for more information
Email address;
Mail address;
*See 5.4. Requesting Claims using Scope Values on the OIDC website for more information
The text was updated successfully, but these errors were encountered: