Files

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

1.0 KiB

Raw Blame History

Public HTTPS domain for broker callbacks

Google brokering을 반복 테스트할 때는 Cloudflare named tunnel + 관리 도메인을 기본 profile로 사용한다. trycloudflare.com quick tunnel과 임의 ngrok URL은 일회성 데모용이며 고정 callback으로 간주하지 않는다.

설정 순서:

cloudflared tunnel login
cloudflared tunnel create keycloak-patterns
예제 config의 tunnel UUID와 credentials path를 실제 값으로 교체
cloudflared tunnel route dns keycloak-patterns auth.example.test
cloudflared tunnel run keycloak-patterns
Keycloak KC_HOSTNAME과 Google redirect URI를 같은 public host로 설정

컨테이너 안의 127.0.0.1은 cloudflared 컨테이너 자신이므로 origin에는 reverse-proxy:8080 같은 Compose service DNS를 사용한다. 마지막 catch-all ingress는 알 수 없는 hostname을 404로 끝낸다.

실 tunnel 생성과 DNS 변경에는 사용자 소유 계정·도메인이 필요하므로 자동 검증은 ingress 파일의 구조까지만 수행한다.

1.0 KiB Raw Blame History

Public HTTPS domain for broker callbacks

1.0 KiB

Raw Blame History