hihi i am sorry my run me code scope runtime is work
hehehe good
Trisna1337
Pada tanggal Sel, 6 Okt 2020 21:18, Janak Amarasena
menulis:
> Hi All,
>
> As per my understanding OAuth 2(RFC6749) doesn't mandate any specific
> media type to be used in the access token request. The spec implies
>
Janak, thanks for the clarification.
A constraint of the OAuth 2.1 draft is that it adds no new features beyond
what has already been standardised and deployed.
While I am a fan of JSON, supporting both application/x-www-form-urlencoded
and application/json will negatively impact
Hi Aaron,
Let me clarify a bit. What I meant was the spec does not make it mandatory
to use x-www-form-urlencoded I am stating this as I did not see any clause
with the word "MUST" with regard to this. And also what I was asking was
not to change using x-www-form-urlencoded to json. More like
The spec does clearly require form-encoded POST requests to the token
endpoint, it's not just an implication. The requests made include simple
key/value pairs so there's nothing really gained by making this a JSON
post. Changing that at this point would be a drastic breaking change to
pretty much
Hi All,
As per my understanding OAuth 2(RFC6749) doesn't mandate any specific media
type to be used in the access token request. The spec implies application/x-
www-form-urlencoded should be used. Since the media type application/json is
very popular and widely used now, any thoughts on
