PR for ES-1843

[mathiasconradt]

✏️ Changes

The "Try" button of a custom social connection ignored the scope configuration entirely, because it was hardcoded. This should fix it, but please review, I wasn't able to deploy/test this extension anywhere. This PR is based on looking at the code.

📷 Screenshots

See https://auth0team.atlassian.net/servicedesk/customer/portal/34/ESD-1843

🔗 References

See https://auth0team.atlassian.net/servicedesk/customer/portal/34/ESD-1843

🎯 Testing

See https://auth0team.atlassian.net/servicedesk/customer/portal/34/ESD-1843

Configure a custom social connection and change the default scope configuration. The scopes should not be ignored when running the "Try" command.
Before, it was hardcoded as 'openid profile' and ignoring any additional scopes set in the configuration.

✅🚫 This change has been tested in a Webtask

✅🚫 This change has unit test coverage

✅🚫 This change has integration test coverage

✅🚫 This change has been tested for performance

🚀 Deployment

Can this change be merged at any time? What will the deployment of the change look like? Does this need to be released in lockstep with something else?

✅🚫 This can be deployed any time

or
⚠️ This should not be merged until:

• Other PR is merged because REASON
• After date because REASON
• Other condition: REASON

🎡 Rollout

Explain how the change will be verified once released. Manual testing? Functional testing?

In order to verify that the deployment was successful we will …

🔥 Rollback

Explain when and why we will rollback the change.

We will rollback if …

📄 Procedure

Explain how the rollback for this change will look like, how we can recover fast.

🖥 Appliance

Please review carefully, I wasn't able to deploy/test this extension anywhere. This PR is based on looking at the code.

[zxan1285]

this.state.connection does not update on _save. So you have to re-open modal dialog to update the URL.
I'd suggest this:

var connection = this.state.connectionForm && this.state.connectionForm.getConnection() || this.state.connection;
return [
      window.env.userUrl + '?',
      'response_type=code',
      '&scope=' + encodeURIComponent(connection.options.scope),
      '&client_id=' + window.env.masterClientId,
      '&connection=' + this.state.connection.name,
      '&redirect_uri=' + window.env.manageUrl + '/tester/callback?connection=' + this.state.connection.name
    ].join('');

[mathiasconradt]

I have no way to really test this properly, I have no local test environment. I also am not familiar with this code base of the extension. Please consider my suggestion just as pseudo-code then :)
Happy to go with your suggestion if it works, as I don't have a way to test it. I trust a product engineer here more than my own code.