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>
3.0 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | adapter-outbound-objectstorage-c07 | durable record가 비밀을 담지 않는다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-objectstorage-c07 | 2026-09-01 |
|
|
|
adapter-outbound-objectstorage |
durable record가 비밀을 담지 않는다
DirectTransferSessionRecord의 javadoc 한 줄이 이 sub-scope의 출발점이다 — "Durable non-secret direct-transfer session state; bearer material is deliberately absent."
본문
durable record가 비밀을 담지 않는다는 것이 출발점이다. DirectTransferSessionRecord의 한 줄 javadoc이 그것이다 — "Durable non-secret direct-transfer session state; bearer material is deliberately absent." 저장되는 것은 generation·제약 다이제스트·서명 시각·만료·credential revision·reference revision뿐이고, presigned URI와 서명 헤더는 process-local 캐시에만 남는다.
프로세스가 재시작하면 이미 발급된 grant는 재현되지 않고 "issued direct grant bearer material is unavailable after process restart"로 명시적으로 실패한다 — 조용히 새로 서명해서 두 번째 bearer를 만드는 대신이다.
DirectTransferSessionRecord 참조 위치
:::evidence key="adapter-outbound-objectstorage-c07" alt="코드베이스에서 DirectTransferSessionRecord 를 검색한 출력 10줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="DirectTransferSessionRecord 코드베이스 검색 — 10줄 · exit 0" zoom="true" :::
CAS가 고정하는 순서
SESSION_RESERVED → GRANT_PREPARED → GRANT_ISSUED → DATA_UPLOADED이고, test 이름이 그 순서를 그대로 못박는다 — preparedCasPrecedesSigningAndIssuedCasPrecedesReturningTheBearerGrant. 서명 전에 prepared가 durable해야 하고, bearer를 반환하기 전에 issued가 durable해야 한다.
완료를 지평이 지날 때까지 거부한다
multipart 쪽에서 가장 흥미로운 것은 완료 시점의 admission drain이다. DirectMultipartCompletionVerifier.requireAdmissionDrained는 provider가 "controlled ingress가 비었다"고 권위 있게 말해 주지 않으면, 마지막 grant 만료 + 검증된 시계 오차 + 최대 in-flight 지평 이 지나기 전에는 완료를 거부한다. 이미 발급된 part PUT이 아직 날아가고 있을 수 있기 때문이다. test 이름이 completionHorizonRejectsWhileIssuedPartRequestsMayStillArrive와 lateGrantAdmissionRejectsAfterCompletionFence로 양방향 모두 고정한다.