[linking] - Invalid scopes handling

[lewisdaly]

Goal:

As a user

I want to be informed if the accounts I've selected for linking are not available, or the account actions are not allowed

so that I can restart the linking process from scratch

Acceptance Criteria:

• updated/new sequence diagram with error callback from DFSP for an invalid set of scopes: PUT /consentRequests/{id}/error
• end to end test that produces a PUT /consentRequests/{id}/error for a bad accountId

Complexity: High

Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating

---

Tasks:

• update sequence diagrams and error codes
• update the handling of POST /consentRequests in the thirdparty-api-adapter
• implement a test scenario on the DFSP to call PUT /consentRequests/{id}/error when receiving a bad set of scopes
• handle PUT /consentRequests/{id}/error in the thirdparty-api-adapter
• implement POST /consentRequests in the thirdparty-scheme-adapter inbound
• handle PUT /consentRequests/{id}/error in the thirdparty-scheme-adapter inbound
• implement POST /consentRequests endpoint in the thirdparty-scheme-adapter outbound
• implement validateConsentRequests endpoint in mojaloop-simulator
• end to end test for this error callback on the PISP's side
• add all possible error scenarios
  Done
• Acceptance Criteria pass
• Designs are up-to date
• Unit Tests pass
• Integration Tests pass
• Code Style & Coverage meets standards

Pull Requests:

• feat: implement consentRequests( post and put) endpoints thirdparty-sdk#80
• feat: add consentRequests related endpoints mojaloop-simulator#94
• test: add e2e tests for consentRequests pisp-project#131
• feat: add consentRequests error codes for linking sdk-standard-components#143
• chore: update consentRequests response structure mojaloop-simulator#95
• chore: update consentRequests simulator resp to support all error cases thirdparty-sdk#86

Follow-up:

• N/A

Dependencies:

• N/A

Accountability:

• Owner: TBC
• QA/Review: TBC

[lewisdaly]

I think this one should wait for now - JJ, Michael and I were discussing an update to the PUT /consentRequests/{id} body that would include the accountIdentifier to make the scopes lookup on the DFSP side much easier.

[lewisdaly]

Sequences are updated, so please go ahead.