With galaxy 25.0.2 deployed with helm charts on a k8s cluster, this instance uses oidc to authenticate users with keycloak idp.
After a authentication, users a redirected to callback at https://example.org/myProject/authnz/keycloak/callback?state=… and response for such GET call include a Location header to https://example.org/myProject/myProject/myProject/user/external_ids or
https://example.org/myProject/myProject/myProject/login/start?connect_external_provider=keycloak…. in the case user already exists.
In the case of new users, restart login works and users are able to log without any issue or by manually remove /myProject/myProject/ from browser url.
I do see a cookie galaxy-oidc-login-next with value “/myProject/” and src code
galaxy-25.0.2/lib/galaxy/authnz/custos_authnz.py shows that login_redirect_url was passed as parameter, but don’t understand where this duplication came from.
Is this a bug, a misconfiguration of our local galaxy instance, something related to ingress resource of k8s?
thank you in advance
