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>
13 lines
454 B
Plaintext
13 lines
454 B
Plaintext
차단 해제, 클러스터 재형성 대기...
|
|
|
|
=== [A-2 재실행] volatile 에서 DB 를 내리면 — 세션이 메모리에 있으니 살아남는가? ===
|
|
DB 정지 전 로그인 완료
|
|
deployment.apps/postgres scaled
|
|
postgres 정지
|
|
① 캐시를 가진 노드에서 refresh HTTP 500
|
|
② 새 로그인 HTTP 200
|
|
|
|
=== DB 복구 후 원복 ===
|
|
deployment.apps/postgres scaled
|
|
deployment "postgres" successfully rolled out
|