Replies: 1 comment
-
|
Problem fixed. My Oauth2-proxy config was missing groups so I changed: - --scope=openid profile emailto - --scope=openid profile email groupsnow it works! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Everyone,
Problem:
For some reason the groups=[] is empty and the Google group assigned to the user is ignored. Everyone with a domain matching the config can login and
I followed this tutorial: https://dexidp.io/docs/connectors/google/ but also checked how argocd is doing this since I'm trying to achieve something very similar: https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/google/ . https://docs.skyscrapers.eu/kubernetes/authentication/#google this tutorial is good too
Dex container logs
Google setup
I can also see that the service account is not called as its metrics report no activity
Kubernetes setup:
In a Kubernetes cluster I have:
OAuth2-proxy -> Dex -> Google IdP
For some technical reasons I prefer to not install it as a helm chart
thanks!
Beta Was this translation helpful? Give feedback.
All reactions