Sending scope parameter with a token request is not configurable

[rlee-metrodigital]

Hello this is an inquiry following up on #62 which was created to see if not sending the scope parameter would cause any issues for users changed in #46

This indeed seems to cause an issue for our openid implementation, i.e. the scope is required. So downgrading to 1.5 resolved the issues, the release right before the changes in #46 were applied.

As far as I can tell, configuring the plugin so that that scope parameters can be passed in the token request is not possible and it seems this was planned (noting this comment #62 (comment)).

[ivankorn]

@mjmbischoff would you mind reverting your change?

That makes me pinning version to 1.5 and I can't use any newer one. Looks like there are a few requests for the same.

[michael-doubez]

Hello

I'll rather make it configurable. OpenID connect didn't allow it but providers tend to be less strict.
Especially with jwt token of implicit flow replacing code flow.

I'll schedule it to be in the next release.

[michael-doubez]

@rlee-metrodigital & @ivankorn Version 2.4 of the plugin is configurable - the default being not to send scopes in token request.