Update content-type header to use v1.1

[elnyry-sam-k]

Goal:

As an FSP

I want to use headers to indicate and understand the version supported by a Switch

so that I can then understand compatibility and proceed further with messages

Acceptance Criteria:

• Switch headers use version 1.1 for Content-Type, Accept as relevant for outgoing messages
• Switch headers support both 1.1 and 1.0 for Content-Type, Accept as relevant for incoming messages
• Postman tests verify support for v1.1, v1.0 messages and v1.1 version on Switch messages

Complexity: The header changes need to be made (from v1.0 to v1.1) and corresponding changes in tests

Uncertainty:

Notes:

• v1.1 and v1.0 messages should be accepted by the Switch
• Pass-through messages are not updated
• Only messages originating in the Switch will always use v1.1
• Currently identified: GET /parties which triggers GET /participants and then GET /parties; Error callbacks and PATCH notification
• timeout handler has header version hardcoded to 1.0
• PATCH returns whatever version has been sent by dfsp, the sdk-standard-components method has 1.0 hardcoded. when fixed to 1.1 it returns back 1.1.
• what to do with simulators?

---

Tasks:

• Update content-type, Accept headers to v1.1 as needed in core services for outgoing messages
  • sdk-standard-component
  • sdk-scheme-adapter
  • Decide on the way to pass the api version into central-services-shared methods (switchDefaultHeaders and sendRequest)
  • central-services-shared
  • ALS
  • quoting-service
  • central-ledger
  • transaction-requests (including authorizations)
• Support content-type, Accept headers for both v1.1, v1.0 as needed in core services for incoming messages
  • ALS
  • quoting-service
  • central-ledger
  • transaction-requests (including authorizations)
• Update MojaSim postman tests for the headers
  • create example tests
  • on support for v1.1, v1.0
  • and checks on messages coming out of the Switch (to have v1.1)

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.

Pull Requests:

• content-type and accept header versions are configurable sdk-standard-components#94
• Feature/#1615 content headers sdk-scheme-adapter#199
• Feature/#1615 content headers central-services-shared#251
• Feature/#1615 content headers quoting-service#240
• Feature/#1615 content headers central-ledger#782
• updated shared lib version to allow configurable resource versions account-lookup-service#370
• updated shared lib to support configurable resource api versions transaction-requests-service#53
• updated shared lib version to support configurable api resource versions ml-api-adapter#459
• added sample tests for header v1.1. postman#171

Follow-up:

• N/A

Dependencies:

• N/A

Accountability:

• Owner: TBC
• QA/Review: @elnyry-sam-k