-
Notifications
You must be signed in to change notification settings - Fork 160
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 Azure Integration fails #2334
Comments
I am also trying to integrate Azure OIDC. I somehow followed the tutorial: https://docs.microsoft.com/en-us/power-apps/maker/portals/configure/configure-openid-settings. I was able to properly setup the issuerURL by using the "issue" value provided in the JSON in the "well-known" endpoint. After that, I created a secret for clientID and clientSecret. Finally, I tested and I was able to get to the microsft Login page. However, I hit another barrier. The gitops-server uses a custom unsupported scope "groups". And I get this error: For that I will create another issue... |
@excelsi0r Yeah I encountered the similar issue but some other errors came up. I am using keycloak as a proxy currently and had to add "groups" to the scope. Dex is another option that can provide these scopes. |
I also believe that with custom Dex or a proxy it might be solved. But I don't intend to use them. Thank you anyway! |
Duplicate: #2507 |
just in case anyone is interested, i made it work check #2507 (comment) |
This one can be closed - see above solution or #2745 (comment) |
Changed to a docs issue, to ensure it's covered in the user guide |
Describe the bug
After setting up
oidc-auth
secret and restarting the deployment, the pod goes intoCrashLoopBackOff
state with error:The Azure/Microsoft OIDC URL used is
https://login.microsoftonline.com/organizations/v2.0
. The resulting OIDC config returns "https://login.microsoftonline.com/{tenantid}/v2.0" from the Microsoft side which causes the failure.Environment
To Reproduce
Steps to reproduce the behavior:
Go through setting up OIDC using Azure's OIDC configuration. (I can provide detailed steps on the Azure side if needed.)
Expected behavior
OIDC should work with Azure/Microsoft OIDC.
Actual Behavior
OIDC auth fails to work.
Additional Context (screenshots, logs, etc)
The text was updated successfully, but these errors were encountered: