New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OIDC scope configuration key name mismatch #109
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Hello @kjoconnor Thanks for your issue. You are right. It is clearly a bug. I will fix it now. |
A new release has been done with the fix: v3.0.4 . Should be ok now. |
Thank you for the quick fix! |
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:
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 addedgroups
.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 usesscope
. Not sure which direction you prefer to change it.The text was updated successfully, but these errors were encountered: