OICD 'missing client id' when fetching access and ID token

[BarryCarlyon]

@RealKozie

Why does the endpoint read headers when it’s specified in the docs that the details are supposed to be passed as query params, or is there something wrong with my request (URL)?

Coz Twitch is weird at times.

@RealKozie

my POST request URL within Postman looks like this: https://id.twitch.tv/oauth2/token?client_id=[my-client-id]&client_secret=[my-secret]&code=[the-oauth-code]&grant_type=authorization_code&redirect_uri=http:localhost:3000/users/auth/twitch/callback

Postman web or postman desktop.

Postman web can be weird
And postman might inject it’s own crap

You might want to compare what you are doing with this example server application

I don’t see anything obviously wrong with what you have written, so I don’t know if postman has done a weird or something else is going on.

I wonder if you turned on “oAuth” in the Postman settings and didn’t populate oAuth
So the clientID you specify in query string is being override by the unset one in postman oAuth settings.

Personally I use insomnia over postman and I don’t test oAuth stuff in the tester client I build my webcode for it instead.

@RealKozie

What the right way to pass the required properties?

As the documentation shows.

So it’s a POST submission, posting the items as query string or “normal” URL Encoded Post Form.