fix: show login landing page instead of immediate redirect #14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/login-landing-page"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Unauthenticated visitors see the teaser and a Log In button instead
of being immediately redirected to Keycloak. Friendlier UX and avoids
confusing errors if the OIDC redirect has issues.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
Automated review by pr-reviewer v0.14.0 | Safety Check | anthropic | tracking id
r-bf02cb-c45500This is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — The changes improve UX by showing a login landing page instead of immediate redirect, with no obvious security or logic issues.
This PR replaces an immediate redirect to Keycloak with a friendlier landing page that shows a teaser and login button. The changes are straightforward:
teaser = await _get_teaser()outside the OIDC check so it's available for both pathsRedirectResponse("/auth/login")with_render_login()call_render_login()function that renders an HTML page with teaser text and a login buttonThe logic flow remains correct and the
/auth/loginendpoint is still used (just via a button click instead of automatic redirect). No security concerns or breaking changes identified.