Support for specifying a custom scope

[blake (Blake Erickson)]

Since several people have had issues with OAuth2 providers requring a specific ‘scope’ value:

OAuth2 Basic Support

I ran into a lot of issues as it required the scope to be set to profile .

OAuth2 Basic Support

In fact, no scope has been requested by them at all, they need to make sure they ask for at least the “basic” scope."

https://twitter.com/jmccartie/status/997557366416592896

I went ahead and added support for specifying a custom scope:

Add support for scope and add some missing translations

All you need to do now is specify the scope you want to use in the “oauth2 scope” site setting field.

Enjoy!

[kueda (Ken-ichi)]

How is this scope being sent? I was expecting it to be a GET param, e.g. https://www.myserver.org/path/to/authorize?client_id=CLIENT_ID&redirect_uri=REDIRECT_URI&response_type=code&state=STATE_ID&scope=login, but after setting what seems like the right configs…

… I don’t see the scope param getting included in the oauth2 authorize url when users click the OAuth login button.

[david (David Taylor)]

Try resetting oauth2 authorize options to the default (“scope”), and then set oauth2 scope to login.

[kueda (Ken-ichi)]

Thanks, that did it! Figured I was confused about something.