Hey folks - Today, the token endpoint takes form-encoded inputs, and sends JSON outputs. This requires developers to use both form encoding and a json parser.
Many services expose symmetric APIs for non-browser endpoints. For example, an API call normally takes JSON input and returns JSON output. What do people think about having the token endpoint accept and return JSON? Cheers, Brian _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
