Prove the migration against live directories and fix what that surfaced
All checks were successful
Build and Publish Container Image / build-and-push (push) Successful in 41s
All checks were successful
Build and Publish Container Image / build-and-push (push) Successful in 41s
Finishes the unproven half of gap G04. Running the harness against real LLDAP, OpenLDAP and Keycloak found four defects that the full unit suite passed over. Every LLDAP user search pointed at a branch that does not exist. Config.userOU() defaulted to ou=users while LLDAP stores users under ou=people, and nothing set UserOU. LookupUser, ListUsers and ValidatePassword all derive from it, so all three silently found nothing against a stock LLDAP -- human login included, not only the export. Exposed by an export returning zero users while still emitting a membership referencing uid=admin, a snapshot the repo's own validator rejects. raw_attributes_well_formed, added one workplan earlier, rejected the LLDAP adapter's own _validation_warning annotation, so the exporter's output failed its own validation. Tooling annotations are exempt now, and a test proves the exemption does not weaken the rule. Migrated group memberships were dangling: resolveMemberDN passed a source DN through unchanged while entries were written to the target branch, so groups named entries the migrated directory does not contain. And empty groups could not load at all, since groupOfNames makes member a MUST -- they reference a placeholder entry the LDIF creates, an organizationalRole rather than a person, emitted only when some group needs it. The scenario-c compose file could not start: bitnami/openldap:2.6 does not exist, though it passed docker compose config. Pinned to the image the scenario was proved against. Proof: LLDAP -> export -> validate -> LDIF -> ldapadd into OpenLDAP 1.5.0, every entry added and every member resolving; a realm from the same export imports into Keycloak and serves discovery. KeyCape passes 5/5 conformance checks, a migrated Keycloak 4/5. Relying-party behaviour and MFA against a migrated realm remain unexercised, and credential/MFA migration is not supplied at all, so no harness can establish it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NV9oijZukGyGbRQGGKnK4P Assistant: claude-code Assistant-Model: opus Assistant-Process: 713576@bnt-lap001 Assistant-Session: 384c511d-9bce-4cb8-a676-2aef6c0c8df6
This commit is contained in:
parent
9819250851
commit
e729ad4c28
11 changed files with 427 additions and 26 deletions
|
|
@ -4,7 +4,7 @@
|
|||
# Exports the canonical directory, transforms it into a Keycloak realm, starts
|
||||
# Keycloak over that realm, and runs the external conformance suite against it.
|
||||
#
|
||||
# Prerequisites: docker, docker compose, and `make build` (binaries land in bin/).
|
||||
# Prerequisites: docker, docker compose, and `make -C src build` (root `make build` only compiles; the src target installs into bin/).
|
||||
|
||||
set -euo pipefail
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ die() { echo "scenario-b: $*" >&2; exit 1; }
|
|||
# Check every prerequisite up front: failing half way through leaves a running
|
||||
# stack and a half-written realm, which is harder to diagnose than not starting.
|
||||
for binary in lldap-export keycape-to-keycloak; do
|
||||
[ -x "bin/$binary" ] || die "bin/$binary is missing; run 'make build' first"
|
||||
[ -x "bin/$binary" ] || die "bin/$binary is missing; run 'make -C src build' first"
|
||||
done
|
||||
command -v docker >/dev/null || die "docker is not installed"
|
||||
command -v go >/dev/null || die "go is not installed"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue