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>
B-0 — BFF·Redis 배포와 자동구성 확인 증거
2026-09-04 14:20–14:50 KST
해설: docs/experiment-b0-bff-redis-deploy.md
| 파일 | 무엇을 보여주는가 |
|---|---|
01-deploy.txt |
배포 전 자원, Redis·BFF 롤아웃, 두 노드에 하나씩 배치됨 |
02-autoconfiguration.txt |
첫 조회 시도(파싱 실패)와 외부 진입점 HTTP 200 |
03-beans-analysis.txt |
B-0 의 답 — InMemoryOAuth2AuthorizedClientService, AuthenticatedPrincipalOAuth2AuthorizedClientRepository, Redis·Spring Session 없음 |
b0-bff-login-success-single-replica.png |
replica 1 에서 로그인 성공한 BFF 화면 |
b0-bff-token-boundary.png |
/bff/token-boundary — principal: labuser, accessTokenStoredOnServer: true, browserTokenCount: 0 |
핵심 세 줄
AuthenticatedPrincipalOAuth2AuthorizedClientRepository— 조회 키가 principal 이고 session ID 가 없다. Q1·Q3 문제의 기제가 이 빈 하나에 있다.- Redis 를 붙여도 그건 안 고쳐진다. 저장소 공유와 조회 키는 다른 문제다.
- replica 2개에서는 로그인 자체가 실패한다. 인가 코드 흐름의 왕복 두 번이 같은 인스턴스로 가야 하는데, 인가 요청이 인스턴스 메모리에 있다.