Goal:
As a Hub Operator
I want to _validate error codes on /error requests _
so that only error codes defined in the Specification and Scheme are allowed
Tasks:
Acceptance Criteria:
Pull Requests:
Follow-up:
For documentation purposes, these are the valid incoming error codes:
- Generic communication errors:
- Generic server errors:
- 2000, 2001, 2002, 2003, 2004, 2005
- Generic client errors:
- Client validation errors
- 3100, 3101, 3102, 3103, 3104, 3105, 3106, 3107
- Identifier errors
- 3200, 3201, 3202, 3203, 3204, 3205, 3206, 3207, 3208, 3209, 3210
- Expired errors:
- Payer errors:
- 4000, 4001, 4100, 4101, 4102, 4103, 4200, 4300, 4400
- Payee errors:
- 5000, 5001, 5100, 5101, 5102, 5103, 5104, 5105, 5106, 5200, 5300, 5400
Dependencies:
Accountability:
- Owner: TBC
- QA/Review: TBC
Goal:
As a Hub Operator
I want to _validate error codes on /error requests _
so that only error codes defined in the Specification and Scheme are allowed
Tasks:
Implement validation with regex giving room for Scheme custom errors- will reuse existing validateFSPIOPErrorCode()Acceptance Criteria:
[ ] Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.Pull Requests:
Follow-up:
For documentation purposes, these are the valid incoming error codes:
Dependencies:
Accountability: