DongHyeonkaandClaude Opus 5
6c310c93b7
Neither client had a backchannel logout URL and the BFF has no oidcLogout configuration, so the three candidate paths all answer 302, which is the authentication redirect rather than a handler. Setting the URL on the identity provider alone changed nothing: with a live session, logging the user out emptied the Keycloak side and left the Redis session untouched. Reachability is not the blocker here, since a Keycloak pod fetches the app's public URL with a 200, but that is a property of this tailnet split-DNS lab and is the assumption most likely to fail in production, where it fails silently. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
16 lines
683 B
YAML
16 lines
683 B
YAML
- generic [ref=f53e3]:
|
|
- banner [ref=f53e4]:
|
|
- generic [ref=f53e5]: keycloak-patterns
|
|
- main [ref=f53e6]:
|
|
- heading "Sign in to your account" [level=1] [ref=f53e8]
|
|
- generic [ref=f53e12]:
|
|
- generic [ref=f53e13]:
|
|
- generic [ref=f53e14]: Username or email
|
|
- textbox "Username or email" [ref=f53e17]: labuser
|
|
- generic [ref=f53e18]:
|
|
- generic [ref=f53e19]: Password
|
|
- generic [ref=f53e21]:
|
|
- textbox "Password" [active] [ref=f53e24]: labpass
|
|
- button "Show password" [ref=f53e26] [cursor=pointer]:
|
|
- generic [aria-hidden] [ref=f53e27]:
|
|
- button "Sign In" [ref=f53e30] [cursor=pointer] |