Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conformation of Funds with just content "application/json; charset=utf-8" may not be supported by gateways #50

Open
mohitmadan opened this issue May 24, 2021 · 1 comment

Comments

@mohitmadan
Copy link

In the case of account information multiple Content Type is supported:

    "content": {
      "application/json; charset=utf-8": {
        "schema": {
          "$ref": "#/components/schemas/OBReadConsentResponse1"
        }
      },
      "application/json": {
        "schema": {
          "$ref": "#/components/schemas/OBReadConsentResponse1"
        }
      },
      "application/jose+jwe": {
        "schema": {
          "$ref": "#/components/schemas/OBReadConsentResponse1"
        }
      }
  }

While in case of Confirmation of funds only "application/json; charset=utf-8" is supported.

    "content": {
      "application/json; charset=utf-8": {
        "schema": {
          "$ref": "#/components/schemas/OBFundsConfirmationConsentResponse1"
        }
      }
    }

This is inconsistent and also API Gateway might not support charset encoding validation breaking the specification validation

Can this be made consistent as in case of Account Information Specification

@mohitmadan
Copy link
Author

Specification 3.1.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant