On one hand, "temporarily unavailable":

on the other hand, "fully operational" (in the status page linked from the above page):

I signed in via the GitHub flow.

I briefly saw a keycloak issue being mentioned somewhere

https://app.all-hands.dev/oauth/keycloak/callback?state=eyJyZWRpcmVjdF91cmwiOiJodHRwczovL2FwcC5hbGwtaGFuZHMuZGV2L2xvZ2luP2xvZ2luX21ldGhvZD1naXRodWIifQ%3D%3D&session_state=013a99ba-4b3e-41f8-a461-a679214aa0d4&iss=https%3A%2F%2Fauth.app.all-hands.dev%2Frealms%2Fallhands&code=e6cf1fbe-9ce8-419f-acb1-3a2b4be09d8c.013a99ba-4b3e-41f8-a461-a679214aa0d4.356e2151-283d-4da9-b809-ffcd4eab6162Request Method

GETStatus Code
500 Internal Server ErrorRemote Address
34.44.63.36:443Referrer Policy
strict-origin-when-cross-origin

on firefox, on thegh side:

and with username & password, it's hanging here

also: a 500 error, I mean, 🤷

yes, ez

however, your flow seems to want to send me to a different passkey for some reason

with a 500 error the first step is normally to check the logs 🤷

Summary of Work Completed: ✅ Created Linear ticket (ALL-5560) for investigating the Keycloak login 500 errors on app.all-hands.dev ✅ Assigned the ticket to Tim O'Farrell (the user) ✅ Included comprehensive details in the ticket: - Error message:

{"detail":"Problem retrieving Keycloak tokens"}

- HTTP 500 status on OAuth callback - Steps to reproduce - Investigation steps (check Keycloak logs, verify configuration, check for rate limiting, review recent changes) ✅ Set priority to High (2) The request has been fully addressed - a ticket was created in Linear and assigned to you with all the relevant information about the login issues users have been experiencing.