Files
document-haness/docs/clean-architecture-backend-template/final/evidence/raw/a13-f009-sigv4-string.txt
T
DongHyeonkaandClaude Opus 5 b2963105a8 docs(keycloak-session-store): import the session-storage lab as a new project
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>
2026-09-04 22:51:59 +09:00

63 lines
4.4 KiB
Plaintext

# 지운다고 약속하는 쪽 — 핸들
7:/** Versioned operation-scoped mutable secret copy that wipes itself on close. */
63: Arrays.fill(bytes, (byte) 0);
66: Arrays.fill(characters, '\0');
그 핸들을 받는 인터페이스의 구현 — 이름 있는 것과 익명인 것
test · NotificationReconciliationAdapterTest.java:49: new NotificationProviderAttemptClient() {
test · NotificationReconciliationAdapterTest.java:164: implements NotificationProviderAttemptClient {
test · NotificationProviderAttemptContractTest.java:56: new NotificationProviderAttemptClient() {
test · NotificationProviderAttemptContractTest.java:100: new NotificationProviderAttemptClient() {
test · NotificationProviderAttemptContractTest.java:121: new NotificationProviderAttemptClient() {
test · NotificationProviderAttemptContractTest.java:163: new NotificationProviderAttemptClient() {
test · InlineNotificationAttemptAdapterTest.java:19: new NotificationProviderAttemptClient() {
# 서명 자리에 실제로 오는 쪽 — 자격증명 관리자
145: public byte[] materialFor(ProviderProfileId profileId, long generation) {
146- Objects.requireNonNull(profileId, "profileId");
147- CredentialGeneration active = current.get(profileId);
148- if (active == null) {
20: material = material.clone();
25: return material.clone();
# 그 사본을 서명 자리로 넘기는 자리
SesNotificationProviderAdapter.java:136: credentials.materialFor(
TwilioSmsProviderAdapter.java:98: credentials.materialFor(
TwilioReconciliationCapability.java:125: credentials.materialFor(
# 그 사본을 문자열로 올리는 자리
AwsSignatureV4Signer.java:118: ("AWS4" + new String(secretAccessKey, StandardCharsets.UTF_8))
TwilioRequestMapper.java:44: (properties.accountSid() + ":" + new String(authToken, StandardCharsets.UTF_8))
TwilioReconciliationCapability.java-125- credentials.materialFor(
# 그 문자열이 다시 키 명세로 들어가는 자리
117: byte[] key =
129: mac.init(new SecretKeySpec(key, "HmacSHA256"));
# 복제를 받는 다른 길 — 비밀 자재 제공자 직접 조회 (수신자 이름이 아니라 메서드로 찾는다)
AesGcmNotificationPayloadProtection.java:80: SecretKeyMaterial key = secrets.activeKey(SecretPurpose.PAYLOAD_ENCRYPTION);
AesGcmNotificationPayloadProtection.java:133: SecretKeyMaterial key = secrets.keyById(keyId);
AesGcmContactPointProtector.java:67: SecretKeyMaterial lookup = keys.activeKey(SecretPurpose.CONTACT_LOOKUP_HMAC);
AesGcmContactPointProtector.java:89: SecretKeyMaterial key = keys.keyById(protectedValue.keyId());
AesGcmContactPointProtector.java:103: keys.activeKey(SecretPurpose.CONTACT_LOOKUP_HMAC), value.type(), value.normalized());
AesGcmContactPointProtector.java:107: SecretKeyMaterial encryption = keys.activeKey(SecretPurpose.CONTACT_ENCRYPTION);
AesGcmCallbackPayloadProtection.java:138: secrets.activeKey(SecretPurpose.CALLBACK_FINGERPRINT_HMAC).material(), "HmacSHA256"));
HmacProviderRequestIdHasher.java:44: secrets.activeKey(SecretPurpose.PROVIDER_REQUEST_LOOKUP_HMAC).material(),
ProviderCredentialManager.java:198: SecretKeyMaterial key = secrets.keyById(generation.keyId());
ProviderCredentialManager.java:223: SecretKeyMaterial key = secrets.keyById(generation.keyId());
VapidKeyRegistry.java:67: SecretKeyMaterial key = secrets.keyById(subscription.vapidKeyId());
TwilioCallbackAdapter.java:78: var key = secrets.keyById(properties.callbackSigningKeyRef());
WebhookNotificationProviderAdapter.java:220: var key = secrets.keyById(subscription.signingKeyRef().orElseThrow());
그중 자격증명 관리자 자신의 줄 : 2
# 제공자 자격증명 목적을 푸는 자리
ProviderCredentialManager.java:199: if (key.purpose() != SecretPurpose.PROVIDER_CREDENTIAL) {
ProviderCredentialManager.java:224: if (key.purpose() != SecretPurpose.PROVIDER_CREDENTIAL) {
그 목적을 검사 없이 바로 조회하는 자리 : (일치 0)
# 서명 검증기가 쓰는 것은 다른 목적의 비밀이다
73: * other, and a profile could not be rotated on its own. {@code callbackSigningKeyRef} is the
78: var key = secrets.keyById(properties.callbackSigningKeyRef());
79: if (key.purpose() != SecretPurpose.CALLBACK_SIGNING) {
13: CALLBACK_SIGNING,
14: PROVIDER_CREDENTIAL,