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>
9 lines
271 B
Plaintext
9 lines
271 B
Plaintext
=== IdP 쪽에만 백채널 로그아웃 URL 을 설정한다 ===
|
|
client id: 9055fa46-6abb-4d6d-a339-8a9183bbf26d
|
|
command terminated with exit code 1
|
|
|
|
=== 로그인 상태를 만든다 ===
|
|
(브라우저에 이미 세션이 있다)
|
|
Keycloak 세션: 2
|
|
Redis: 2 키
|