Bug: Keycloak redirects to frontend which redirects to keycloak ad infinitum causing "ERR_TOO_MANY_REDIRECTS",

[corneliusroemer]

I've noticed this both in a local test and on our main deployment: after succesfully logging in as testuser on keycloak, you get redirected back and forth infinitely leading to ERR_TOO_MANY_REDIRECTS

I've tried to reproduce now on main deployment after the first time I got the bug but I can't find ways to trigger it reliably. But here are some screenshots:

Potentially reproducible if logging out then clicking on user.

[corneliusroemer]

It happens in my main browser (Brave), but not in incognito. Can't reproduce in Chrome. Maybe some extension thing? But still something is up.

[fengelniederhammer]

I also saw this on Firefox. I think something doesn't work as reliably as we thought. We'll definitely have to check this. But anyway we have to improve certain aspects of the whole login management in the browser anyway.

[corneliusroemer]

Some pre-emptive logging in the middleware could help to figure out what's going on when someone manages to catch the issue.

[corneliusroemer]

Just got that error again, when clicking "approve" on 28 sequences. Strange.

Now it happens for anything I click that requires authentication.

[corneliusroemer]

Hit this error after a few clicks, following a standard test flow of submission, then navigating to revision.

[JonasKellerer]

I thought a little about it and tried something in https://github.com/pathoplexus/pathoplexus/pull/653.
Could you check if your problem still occurs?

[JonasKellerer]

It seems that the preview does not work here. I'm still looking at it.

[corneliusroemer]

Thanks for looking into this @JonasKellerer! Preview indeed gives me 500 after successful login on pages requiring authentication

[corneliusroemer]

Is this fixed now by #638 or does this only add logging in this situation? @JonasKellerer

[fengelniederhammer]

Did this happen ever again or can we close this?

[chaoran-chen]

I'll close this. @corneliusroemer, please reopen if this is still an issue!

[corneliusroemer]

Yep no longer an issue!

[corneliusroemer]

Now getting it again, related to #1090 which tries to fix #1087