Does scope have to be at the end of the authorize request?

[BarryCarlyon]

@no_skills_ben

It was working without any errors but would refuse to give me any scopes back. I was using ‘+’ for spaces and I tried encoding the url and not encoding the url diffrent scopes, 1 scope, nothing worked.

I finally just put the &scope= at the very end of the string after the state and it suddenly started working. any insights in this? I can post the code but honestly I need to rewrite it so it’s not a giant example of bad coding practices.

Getting Status 400 while OIDC Authorization

We are following this documentation OIDC Authorization Code Flow Trying to get UserID and StreamKey. Our GET Call https://id.twitch.tv/oauth2/authorize?response_type=token+id_token&client_id=(our_clientid)&redirect_uri=(our_uri_address)&scope=user_read+channel_read+openid&state=c3ab8aa609ea11e793ae92361f002671&claims={"id_token":{"email":null,"email_verified":null%20},"userinfo":{"picture":null}} We get as a response: {“status”:400,“message”:“invalid scope: ‘openid’ required for ‘id_token’ r…

You basically sound like a similar problem as described here.

You didn’t URLencode your redirect_uri so you accidentally merged your redirect URL with the rest of the arguments. Or some other odd combination of fields resulting in things not parsing as expected twitch side.

Scope doesn’t need to be at the end, the argument order doesn’t matter.

I’d know for sure if you provide the actual URLs you have tried/generated