DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
26 lines
1.2 KiB
Plaintext
26 lines
1.2 KiB
Plaintext
=== [현재] 같은 사용자의 항목 ===
|
|
client_registration_id | principal_name | access_token_issued_at | at_md5
|
|
------------------------+----------------+----------------------------+----------------------------------
|
|
keycloak | labuser | 2026-09-04 05:10:46.927192 | 675af2286bfc2fd9d2bab7bc8f391df7
|
|
(1 row)
|
|
|
|
행 수: 1
|
|
|
|
=== [모의 두 번째 브라우저] 세션만 지우고 같은 사용자로 다시 로그인시킨다 ===
|
|
(브라우저가 달라도 principal 은 같으므로 조회 키가 같다)
|
|
Redis 세션 삭제 완료 — 다음 요청이 새 로그인을 만든다
|
|
=== [재로그인 후] 행이 늘었는가, 덮어써졌는가 ===
|
|
client_registration_id | principal_name | access_token_issued_at | at_md5
|
|
------------------------+----------------+----------------------------+----------------------------------
|
|
keycloak | labuser | 2026-09-04 05:12:13.018828 | e19a63fc5aa18bd0a68b3e19dff16b3b
|
|
(1 row)
|
|
|
|
행 수: 1
|
|
|
|
★ 행 수가 1 그대로이고 md5 가 바뀌었으면 → 덮어쓰기다
|
|
|
|
=== Q1 검증 ④ — 로그아웃하면 두 저장소가 다 정리되는가 ===
|
|
로그아웃 전
|
|
Redis: 1 키
|
|
PostgreSQL: 1 행
|