With the FRONTEND_URL fix (#107) the auth-api now boots, and the conformance run gets far enough to bring up the adapter — which then exits (surfaced by the new setup-failure log dump):
adapter-1 | Error: cookieSecret must be at least 32 characters...
dependency failed to start: container seamless-verify-adapter-1 exited (1)
The adapter reuses API_SERVICE_TOKEN as its COOKIE_SIGNING_KEY, and seamless verify defaulted the token to "verify-dev-service-token" (24 chars). A newer @seamless-auth/express rejects a cookie secret shorter than 32.
Fix: default the dev service token (and bootstrap secret) to >=32-char constants in src/commands/verify.ts.
With the FRONTEND_URL fix (#107) the auth-api now boots, and the conformance run gets far enough to bring up the adapter — which then exits (surfaced by the new setup-failure log dump):
The adapter reuses
API_SERVICE_TOKENas itsCOOKIE_SIGNING_KEY, andseamless verifydefaulted the token to"verify-dev-service-token"(24 chars). A newer@seamless-auth/expressrejects a cookie secret shorter than 32.Fix: default the dev service token (and bootstrap secret) to >=32-char constants in
src/commands/verify.ts.