[Openid-specs-ab] Issue #1564: Request body data encoding for credential endpoint as JSON instead of form encoding (openid/connect)

[Tobias Looker]

New issue 1564: Request body data encoding for credential endpoint as JSON instead of form encoding
https://bitbucket.org/openid/connect/issues/1564/request-body-data-encoding-for-credential

Tobias Looker:

Currently the spec defines the request body as form encoded rather than JSON which is inconsistent with the response body format. I would like to propose that we change the request body encoding to JSON instead as this improves debugging especially for credential requests that contain nest JSON objects as parameter values.