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>
19 lines
608 B
Plaintext
19 lines
608 B
Plaintext
=== 비교를 위해 세션을 비운다 ===
|
|
DELETE 151
|
|
|
|
=== volatile 모드로 전환 ===
|
|
namespace/keycloak-lab unchanged
|
|
secret/keycloak-lab-secrets configured
|
|
persistentvolumeclaim/postgres-data unchanged
|
|
deployment.apps/postgres unchanged
|
|
service/postgres unchanged
|
|
statefulset.apps/keycloak configured
|
|
service/keycloak-headless unchanged
|
|
service/keycloak unchanged
|
|
ingress.networking.k8s.io/keycloak unchanged
|
|
Waiting for 1 pods to be ready...
|
|
partitioned roll out complete: 2 new pods have been updated...
|
|
|
|
=== [검증] 정말 꺼졌는가 ===
|
|
["start","--features-disabled=persistent-user-sessions"]
|