OIDC scope configuration key name mismatch

[kjoconnor]

Describe the bug
The documentation as well as the helm chart differ from the source code in regards to OIDC scope specification.

To Reproduce
Configure an OIDC provider:

authProviders:
  oidc:
    provider1:
      scopes:
        - openid
        - email
        - profile
        - groups

Browse to s3-proxy unauthenticated and you will be redirected to the OIDC provider, but it will only have requested the default scopes of [ openid, email, profile ], it will not have added groups.

Expected behavior
I would expect all of the scopes I requested be added to the auth request to the OIDC provider.

Version and platform (please complete the following information):
Running on k8s 1.19 on IBM Cloud, with the latest helm chart and s3-proxy image.

Additional context
It seems to just be a mismatch between the documentation as well as helm chart and the code. The docs and helm chart say to use scopes, but the code itself uses scope. Not sure which direction you prefer to change it.

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.77. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[oxyno-zeta]

Hello @kjoconnor

Thanks for your issue. You are right. It is clearly a bug. I will fix it now.
It will be "scopes".

[oxyno-zeta]

A new release has been done with the fix: v3.0.4 . Should be ok now.

[kjoconnor]

Thank you for the quick fix!