Developers

Run Covenant against a sample app.

Exercise the Northline OpenID Connect client and workspace access in a loopback environment with synthetic identities.

Northline sample Loopback only

Local OpenID Connect client

  • Client IDnorthline-sample
  • FlowCode + PKCE S256
  • Callbacklocalhost:3001/callback
Browser smoke test

Run the example in Chrome

  1. Start local KeycloakPort 8180
  2. Keep these ports free3000 and 3001
npm run test:browser

Prepare the local runtime

From the Covenant project directory, use Node.js 22.23.1 or later, Keycloak 26.8.2, and a patched Java 21 LTS build. Set JAVA_HOME to your JDK, then replace the example path with your Keycloak directory. The local preparation command writes credentials to ignored files.

Terminal one
npm ci --ignore-scripts
npm run local:prepare
npm run local:idp -- /path/to/keycloak-26.8.2

Verify sign-in in Chrome

Leave Keycloak running on port 8180 and free ports 3000 and 3001. The browser test starts an isolated console, creates and removes synthetic accounts, and checks passkey enrollment, fresh verification, and reseller isolation. It exchanges a code for the Northline client and verifies refresh-token rotation.

Terminal two
npm run test:browser

Inspect the Northline client settings

The sample uses a pre-registered public client with the openid scope and authorization code with PKCE S256. Use the exact callback URL and the issuer’s discovery document at /.well-known/openid-configuration. Production client registration is pending.

Issuer
http://localhost:8180/realms/authcan-local
Client ID
northline-sample
Callback URL
http://localhost:3001/callback