You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When logging in via Google SSO, user permissions are not working correctly despite proper RBAC configuration. While authentication is successful, the user account appears to not exist in the system ("account does not exist" error) and has no admin permissions even though they are explicitly granted in the RBAC configuration.
To Reproduce
Configure Argo CD with Google SSO authentication and RBAC as shown in the configurations below
The issue is that the initial configuration is missing explicit scope definitions for group and email claims. Without these scopes, Argo CD’s Dex connector does not request (or properly map) the required user information (such as groups) from Google. Consequently, the RBAC engine never sees the necessary claims to match the policy (for example, mapping “[email protected]” to an admin role)
The fix is to explicitly configure the scopes in both the Dex configuration and the RBAC ConfigMap. The working solution includes:
In the argocd-cm ConfigMap (Dex configuration):
Add the userInfoPath to explicitly fetch user details.
Specify the required OAuth scopes (openid, profile, and email) so that the token contains the necessary claims.
In the argocd-rbac-cm ConfigMap:
Add the scopes: '[groups, email]' field to ensure that Argo CD processes the group and email claims from the token.
Describe the bug
When logging in via Google SSO, user permissions are not working correctly despite proper RBAC configuration. While authentication is successful, the user account appears to not exist in the system ("account does not exist" error) and has no admin permissions even though they are explicitly granted in the RBAC configuration.
To Reproduce
argocd account get argocd account can-i delete applications '*/*'
Current Configuration
argocd-cm:
argocd-rbac-cm:
Expected behavior
Actual behavior
Version Information
The text was updated successfully, but these errors were encountered: