Hosted login

Send customers to a hosted sign-in page.

Your application starts an OpenID Connect sign-in. Covenant handles the identity check and returns the browser to your registered callback.

Northline sample Demo

Sign in to Northline

  • Accountalex@northline.example
  • Sign-in methodPasskey
  • StatusWaiting for confirmation
OpenID Connect

Sign-in flow

  1. Request authorizationPKCE request created
  2. Confirm identityWaiting for passkey
  3. Return to the appWaiting for authorization code

The sign-in flow

The Northline sample verifies the complete exchange against the local Keycloak setup.

  1. Start in your app

    Your app creates a sign-in request and remembers the state, nonce, and PKCE verifier for that attempt.

  2. Open hosted sign-in

    The browser opens Covenant as a top-level page. The user completes the identity check there.

  3. Return to your app

    Your app receives a short-lived authorization code at its registered callback, exchanges it with the PKCE verifier, and validates the ID token before starting a session.

What the local build verifies

The console redirects the browser to the hosted identity provider. Production client registration, callback approval, recovery, and provider review are release gates.

Protocol
OpenID Connect authorization code flow with PKCE S256
ID token checks
Signature, issuer, audience, and nonce
Sign-in attempt
Single use with a five-minute expiry