SDK-Scheme-Adapter validates Inbound FSPIOP request content-type headers

[mdebarros]

Goal:

As a SDK-Scheme-Adapter User

I want to ensure that the SDK-Scheme-Adapter validates Inbound FSPIOP request content-type headers

so that the header validation conforms to the FSPIOP Specification

Acceptance Criteria:

• FSP Inbound request headers are validated against the FSPIOP content-type specification throwing an FSPIOP Error: 3001 - Unacceptable version requested (ref: https://docs.mojaloop.io/mojaloop-specification/fspiop-api/documents/API%20Definition%20v1.1.html#table-112)

• FSP Inbound request content-type header is correctly matched to the operation (i.e. transfers, parties or participants) throwing an FSPIOP Error: 3001 - Unacceptable version requested (ref: https://docs.mojaloop.io/mojaloop-specification/fspiop-api/documents/API%20Definition%20v1.1.html#table-112)

Complexity: Medium

Uncertainty: Medium

---

Tasks:

• TBD [ @? ]

Done

• Acceptance Criteria pass
• Designs are up-to date
• Unit Tests pass
• Integration Tests pass
• Code Style & Coverage meets standards
• Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
• TBD

Pull Requests:

• feat(#2264): add more robust header validation for inbound server sdk-scheme-adapter#278

Follow-up:

• SDK Scheme Adapter is not accepting PUT /parties with 1.1 content-type header #1891

Dependencies:

• N/A

Accountability:

• Owner: TBC
• QA/Review: TBC

[mdebarros]

Initial thinking on how to resolve this --> mojaloop/sdk-scheme-adapter#276

However, much re-factoring required on unit/integration tests.