PT-AM-CPE practice question 12 of 35

To ensure the user's full name is displayed on the consent screen for an OpenID Connect application, which string should be added into the Support Claims property on the OpenID Connect tab page of the OAuth2 Provider service in PingAM?

Full set: 100 questions
Answer options
A: name|en|Full name Correct answer
B: Full name|en|name
C: full_name|Full name
D: name|en|given_name+' '+family_name
Correct Answer:
A. name|en|Full name
Explanation

To configure a claim for display on the OpenID Connect consent screen in PingAM, the Supported Claims property of the OAuth2 Provider service must be updated. The required format for each entry is a pipe-delimited string: claim-name|locale|description. In this case, name is the standard OIDC claim for the user's full name, en is the locale for English, and Full name is the desired descriptive text to be shown to the end-user. This configuration makes PingAM aware of the claim and how to present it during the consent step.

Why Incorrect

B. Full name|en|name: This incorrectly places the description in the claim name position and the claim name in the description position.
C. fullname|Full name: This format is missing the required locale. Also, fullname is not the standard OIDC claim for a user's full name; name is.
D. name|en|givenname+' '+familyname: The description field is for a static, human-readable string, not for scripting or attribute mapping expressions.

References

Ping Identity Documentation, PingAM > Configuration > Services > OAuth 2.0/OpenID Connect > To Configure the OpenID Connect Provider. The documentation specifies the format for the "Supported Claims" property as claim-name|locale|description. (Accessed via Ping Identity Knowledge Base and official product guides).

OpenID Connect Core 1.0 specification, Section 5.1 Standard Claims. This standard defines name as the claim for the End-User's full name.

Scroll to Top