DongHyeonkaandClaude Opus 5
8f6d67df35
Disabling persistent-user-sessions moves the session from PostgreSQL into the cluster, and the A-1 and A-8 outcomes flip to 400 Session not active while a new login during database loss starts working. The control group in each case still returns 200, so the injections cut only what they were meant to cut. This is the pair that makes the A layer legible: the conventional wisdom that sessions ride TCP 7800 is correct for Keycloak 24 and earlier, and the mistake is applying it to 26 without checking the version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
14 lines
483 B
Plaintext
14 lines
483 B
Plaintext
=== [A-8 재실행] 재시작 전 로그인 ===
|
|
sid = aVwYnzKZFFvMqD3bpSeiILuM
|
|
|
|
=== 롤링 재시작 ===
|
|
statefulset.apps/keycloak restarted
|
|
partitioned roll out complete: 2 new pods have been updated...
|
|
|
|
=== ★ 재시작 전 토큰이 아직 통하는가 (persistent 였을 때는 200) ===
|
|
keycloak-0 에서 refresh HTTP 400
|
|
--- 오류 본문 ---
|
|
{"error":"invalid_grant","error_description":"Session not active"}
|
|
=== 캐시 상태 ===
|
|
keycloak-1 sessions 캐시 1.0 건
|