Two social (GitHub) connections for different scopes

[stephanie.chamblee]

Hi @martincura,

You may be able to simplify this by using the same github connection and passing the additional scopes in the connection_scope param from the application that needs it when it makes the /authorize request.

You can read the details of this approach in this FAQ:

Pass additional scopes/permissions to a Social Connection

Question: Can I add additional scopes to a Social Connection if I don’t see them in the permissions list? When you configure a Social Connection, Auth0 gives you the option to configure additional permissions (scopes) to request to the identity provider, so that your application can use the identity provider access token to access other protected resources (see Identity Provider Access Tokens for instructions on how to obtain these tokens). The Google Social Connection, for example, shows this…

And in the docs:

Add Scopes/Permissions to Call Identity Provider APIs