DongHyeonkaandClaude Opus 5
98a74e90a5
The forward upgrade to 26.7.3 was zero downtime across 87 samples, and since databasechangelog stayed at 210 the rollback to 26.7.0 also succeeded, which narrows D-2's conclusion: rolling back fails when the schema moved, not because of the version number. The row count is the check. Role changes never reach the upstream through request repetition; the session is a snapshot taken at login and only a new session picks up the new claim. Auditing the docs also surfaced that Prometheus scrapes only keycloak, kubelet, node-exporter and itself, so the B-layer experiments have no metrics to screenshot rather than missing screenshots. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
10 lines
337 B
Plaintext
10 lines
337 B
Plaintext
=== ★ Keycloak 에서 email 을 바꾼다 ===
|
|
변경 시각: 15:27:52
|
|
IdP 의 값: [ {
|
|
IdP 의 값: "email" : "changed-labuser@example.com"
|
|
IdP 의 값: } ]
|
|
|
|
=== IdP 쪽 세션과 oauth2-proxy 세션 ===
|
|
Redis 세션: 1 개
|
|
(세션은 로그인 시점의 클레임을 담고 있다 — 이제 요청을 반복해 본다)
|