| Name | Verify that the ID Token returned during Authorisation redirect does not contain personal claims |
|---|
| Category | INFOSEC |
|---|
| Execution Method | AUTOMATED (FAPI BASELINE) |
|---|
| Preconditions | |
|---|
| Description | In this particular test the Recipient initiates a consent flow that requests ongoing access. The Data Holder provides an ID Token during the initial authorisation redirect (post /authorize) which must not contain personally identifiable information |
|---|
| Steps | - Establish a consent agreement using the authorisation flow and receive the redirect containing the code and id_token attributes
- Verify that the redirected id_token does not contain any of the standard PII claims including:
- name
- given_name
- family_name
- middle_name
- nickname
- preferred_username
- profile
- picture
- website
- email
- email_verified
- gender
- birthdate
- zoneinfo
- locale
- phone_number
- phone_number_verified
- address
|
|---|
| Inputs | Established Dynamic Client Registration |
|---|
| Expected Results | The Holder should not include any of the specified claims in the authorisation endpoint returned ID Token |
|---|