You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Goal:
As a
userI want to
be informed if the accounts I've selected for linking are not available, or the account actions are not allowedso that
I can restart the linking process from scratchAcceptance Criteria:
PUT /consentRequests/{id}/error
PUT /consentRequests/{id}/error
for a badaccountId
Complexity: High
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
POST /consentRequests
in the thirdparty-api-adapterPUT /consentRequests/{id}/error
when receiving a bad set of scopesPUT /consentRequests/{id}/error
in the thirdparty-api-adapterPOST /consentRequests
in the thirdparty-scheme-adapter inboundPUT /consentRequests/{id}/error
in the thirdparty-scheme-adapter inboundPOST /consentRequests
endpoint in the thirdparty-scheme-adapter outboundmojaloop-simulator
Done
Pull Requests:
Follow-up:
Dependencies:
Accountability:
The text was updated successfully, but these errors were encountered: