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
I followed this link to test integrating Azure AD with Argocd login.
For #3, Azure AD App Registration Auth using Dex, it says to follow the same steps as in step 2 with different configurations.
Authentication via OIDC and RBAC worked fine with step 2.
In step 2, the user info showed the group I specified as the SSO target.
However, when I follow step 3, it shows all the tenant groups that I belong to, not the group that I targeted for SSO.
The target group registered in the enterprise app is the same for both.
To Reproduce
Expected behavior
Sign in with a user account that belongs to the SSO target group, and assign RBAC according to the policy.
But it looks like worked as default reader role. RBAC is not working so I can't create app.
Checklist:
argocd version
.Describe the bug
https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/microsoft/#azure-ad-app-registration-auth-using-dex
I followed this link to test integrating Azure AD with Argocd login.
For #3, Azure AD App Registration Auth using Dex, it says to follow the same steps as in step 2 with different configurations.
Authentication via OIDC and RBAC worked fine with step 2.
In step 2, the user info showed the group I specified as the SSO target.
However, when I follow step 3, it shows all the tenant groups that I belong to, not the group that I targeted for SSO.
The target group registered in the enterprise app is the same for both.
To Reproduce
Expected behavior
Sign in with a user account that belongs to the SSO target group, and assign RBAC according to the policy.
But it looks like worked as default reader role. RBAC is not working so I can't create app.
Screenshots
Version
Logs
I used helm chart.
OIDC values.yaml
DEX values.yaml
OIDC app manifest
DEX app manifest
argocd pod log
The text was updated successfully, but these errors were encountered: