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>
29 lines
758 B
Plaintext
29 lines
758 B
Plaintext
=== 로그아웃 전 상태 ===
|
|
Redis: 2 키
|
|
keycloak-patterns 세션: 0
|
|
|
|
=== ★ IdP 로그아웃 — Keycloak 이 백채널 알림을 보낼 것이다 ===
|
|
시각: 14:53:29
|
|
|
|
=== Keycloak 로그 — 백채널 요청을 보냈는가, 결과는 ===
|
|
|
|
=== BFF 로그 — 백채널 요청이 도착했는가 ===
|
|
|
|
=== 앱 세션이 정리되었는가 ===
|
|
Redis: 2 키
|
|
_oauth2_proxy-6b028a70f69c8f0da9966eb36972dff2
|
|
bff:session:sessions:6e0d9af4-2c8f-47d2-bf83-8b1e9670c679
|
|
=== 로그아웃 전 — 실제 세션이 있는가 ===
|
|
keycloak-patterns 세션: 1
|
|
Redis: 1 키
|
|
|
|
=== ★ IdP 로그아웃 → 백채널 알림 ===
|
|
시각: 14:54:21
|
|
|
|
=== Keycloak 로그 ===
|
|
|
|
=== BFF 로그 — 요청이 왔는가 ===
|
|
|
|
=== 앱 세션 ===
|
|
Redis: 1 키
|