-
Notifications
You must be signed in to change notification settings - Fork 822
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-authservice: infinite redirect loop with v1.7.0-rc.2 #2423
Comments
I tried same setup with the latest image from oidc-athservice, it worked. changed image from https://console.cloud.google.com/gcr/images/arrikto/global/oidc-authservice |
Updating to this image |
This works for me too. |
The given image does not work in KF, this commit updates it from gcr.io/arrikto/kubeflow/oidc-authservice:e236439 to gcr.io/arrikto/oidc-authservice:0c4ea9a , note that registry link and tag is updated. fixes kubeflow#2423
@deepk2u I haven't managed to reproduce this in the latest version of KF 1.7. Could you share steps to reproduce? |
@kimwnasptd I am not using dex, I am trying to connect to Intuit's OIDC directly using the above config. exact same config works for the new version of authservice. |
/close We are not at Kubeflow 1.8 |
@juliusvonkohout: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I am trying to test v1.7.0-rc.2 and i see the oidc-authservice image tag is moved from
28c59ef
toe236439
83fbc57
i see the new version requires some more parameters or changed parameter names like
AUTHSERVICE_URL_PREFIX
andSKIP_AUTH_URI
changed toSKIP_AUTH_URLS
I provided all the parameters accordingly, but I am seeing this issue of infinite redirect.
Flow:
REDIRECT_URL
config:
I checked the logs and looks like the session key is not getting stored properly, so it always tries to fetch the new codes by restarting the OIDC MFA flow.
The text was updated successfully, but these errors were encountered: