Files
clean-architecture-backend-…/infra/keycloak
DongHyeonkaandClaude Opus 5.5 016597ac78 review-followup Wave 2: 정합성 수정 통합과 검증, 현황표·재개 프롬프트
13개 작업 묶음(P1–P13)의 W2 커밋을 합치고 전체 게이트로 검증했다.

- 묶음별 정합성 수정(notification dispatch·recovery, object storage staged
  publication, fileserver 복구·정리, gRPC 플랫폼, Redis 분류·lease TTL, JPA
  outbox claim 순서·durable operation HTTP, web 요청 id·category 필수, graphql
  에러 mapper, Mongo profile 바인딩, build 소스 보존 게이트·compose smoke info 확인)
- 통합 때 드러난 3건 수정: outbox claim 테스트 fixture의 가짜 envelope hash,
  sample scan이 새 operation controller를 등록하던 문제, SpotBugs aux classpath
  파일이 truncate되지 않아 로컬에서 ".jar.jar"로 실패하던 문제
- 현황표: 묶음 결과 반영, 소유자 결정 21–27, 후속 발견 결함 47행, 요약 갱신
- docs/capability-status.md 「제거된 코드」에 85행 추가
- 묶음 결과 파일·에이전트 지시·스크립트를 docs로 옮기고 desktop 재개 프롬프트 추가

검증: check, ci verifyDependencyLocks, mainCheck, architecture/public path/env
keys/config contract, bootstrap·sample integration/system, build-logic·build-tools
test, optional-platforms ci, qualificationBootJar 통과. integrationCheck는 이번
작업 전에도 실패하던 lane(Redis topology 모드 인자, httpclient failure
injection, AWS 보호 lane)만 실패.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-28 14:46:30 +09:00
..

Keycloak realm artifact

realms/ca-skeleton-realm.json is imported by the keycloak service in docker-compose.infra.yml and is the same realm every GraphQL qualification lane authenticates against.

The client secret is a reference, never a value

The confidential client ca-skeleton-api carries "secret": "${KEYCLOAK_GRAPHQL_SMOKE_CLIENT_SECRET}". entrypoint.sh reads the value from the Compose secret mounted at /run/secrets/keycloak-graphql-smoke-client-secret, exports it, and execs kc.sh start-dev --import-realm, so the value never reaches Git, a rendered Compose config, a command line, or an evidence file. A realm file with a working credential in it is a credential in the repository, and "it is only for smoke tests" is not something a scanner or a fork can tell.

No comment keys in the realm JSON

Keycloak deserializes this file into RealmRepresentation with unknown fields rejected, not ignored. A "_comment" key here fails the whole import with Unrecognized field "_comment", the container exits 1, and the lane fails on Keycloak rather than on anything it was testing. That is why this rationale lives in Markdown next to the artifact instead of inside it.

What the realm grants

  • realm role user — the baseline role the application authorizes ordinary calls on
  • client role ca-skeleton-api:graphql-query — permission to execute a GraphQL query
  • a service account for the client-credentials grant the qualification lane uses
  • audience and realm/client role mappers, so the issued token carries what the resource server validates

Standard flow and direct access grants are disabled: the lane authenticates as a service, and an enabled password grant is a second way in that nothing tests.