| Name | Verify that a Pairwise Identifier is unique between recipients |
| Category | INFOSEC |
| Execution Method | AUTOMATED (FAPI BASELINE) |
| Preconditions | |
| Description | In this particular test we initiate consents with two different Recipient accounts and then verify that the pairwise identifier supplied back is different. |
| Steps | The authorisation flow should be executed consistently between recipients. Data Recipient 1 - Establish a consent agreement using the authorisation flow and receive the redirect containing the code and id_token attributes
- Perform Token retrieval using a POST /token
- Record the sub claim within the id_token
- Establish a new consent agreement using the authorisation flow and receive the redirect containing the code and id_token attributes
- Perform Token retrieval using a POST /token
- Verify that the sub returned in (3) matches the one returned within the id token obtained in (5)
- (For Joint Accounts) Establish a consent agreement as Party A using the authorisation flow and receive the redirect containing the code and id_token attributes.
- Perform Token retrieval using a POST /token
- Record the sub claim within the id_token
- Establish a consent agreement as Party B using the authorisation flow and receive the redirect containing the code and id_token attributes.
- Perform Token retrieval using a POST /token
- Record the sub claim within the id_token
- Verify that the sub from (b) does not match (e)
Data Recipient 2- Establish a consent agreement using the authorisation flow and receive the redirect containing the code and id_token attributes
- Perform Token retrieval using a POST /token
- Record the sub claim within the id_token
Post- Verify that the sub recorded from Data Recipient 1 is different from the sub recorded from Data Recipient 2
|
| Inputs | - Established Dynamic Client Registration
- ID Token is verified to contain a sub
|
| Expected Results | - The Holder must not be issuing duplicate sub's
- The Holder must be issuing the same sub across consents for the same data recipient
|