![](https://seccdn.libravatar.org/avatar/008a8db3f6a813af5f8064f2be96e100.jpg?s=120&d=mm&r=g)
Thanks, Christian.
On Thu, Oct 28, 2021 at 2:26 PM Christian Boltz
Lars and I looked at the issue - both on the login proxy and the apache log on the forums server. Unfortunately we didn't find any obvious problems, and ran out of ideas what could cause the breakage :-(
The interesting part is that logging in to other services that also use the login proxy (like the wikis and progress.o.o) works without problems.
Actually I just found a workaround: - login on progress.opensuse.org or one of the wikis - go to forums.opensuse.org, and you are logged in
That doesn't solve the issue, but at least it's a workaround - and maybe it gives someone an idea where to look for the real issue.
That's very strange. I've been trying off and on today, between meetings, to see if I could get in - I had tried logging into Bugzilla (for example), and actually was able to log in once, but after that first time, upon submitting username/password, I was just getting bounced back to the login page. I just tried that again, and got logged into Bugzilla, but it didn't carry the login over to the forums. What I see when I run a trace is that the authentication goes to https://forums.opensuse.org/ICSLogin/auth-up after entering credentials on the page at https://forums.opensuse.org/ICSLogin/auth-up?url=%2F (after clicking the login link), and it sits on that auth-up page for about 2-3 minutes before the gateway times out. So it seems that whatever is happening behind the scenes at that auth-up URL is not responding. Trying to trace the authentication flow itself (I use a Chrome plugin called "rcFederation Tracer", which traces SAML, OAuth/OIDC, and WS-* protocols), I don't see any data at all. Logging into the wiki first does work for me. I don't know a lot about how the forum authentication configuration is set up - it's not something that is done through the forum admin control panel, and I wasn't involved in that piece of the configuration. Can either of you see where the auth-up URL is supposed to be trying to connect to?