FAPI part 2: Request object POST should have Content-Type: application/jose

[Vladimir Dzhuvinov]

The example has "application/jws":

https://openid.net/specs/openid-financial-api-part-2-ID2.html#request

The proper content type is "application/jose":

https://tools.ietf.org/html/rfc7515#section-9.2.1

I suppose "application/jwt" could also work:

https://tools.ietf.org/html/rfc7519#section-10.3.1

[Dave Tonge]

Thanks - this is a good point.

We want to split this part into a new draft, so I’ll leave this issue open for now.

[Dave Tonge]

Assigned to new component.

Draft under way: https://bitbucket.org/openid/fapi/branch/pushed_request_uri

[Nat Sakimura]

The example has "application/jws":

https://openid.net/specs/openid-financial-api-part-2-ID2.html#request

The proper content type is "application/jose":

https://tools.ietf.org/html/rfc7515#section-9.2.1

I suppose "application/jwt" could also work:

https://tools.ietf.org/html/rfc7519#section-10.3.1

[Torsten Lodderstedt]

no longer applicable since the draft was changed to use application/x-www-form-urlencoded