Login returns 200 and the session never starts
What we saw
Sign-in answered 200 OK and redirected, and every following page acted as if you were signed out.
How we found it
curl -i on the login response. The Set-Cookie header was wrapped in quotes. Several iterations had been spent before that on the proxy and on front-end hydration.
Cause
The session token was base64 with = padding at the end. The framework quoted the cookie value because of the =, and each layer read it differently, so the signature never matched.
Fix
Base64url without padding for the token.
The rule now
Look at the real header before you reason about the code.