One site. Its own account experience.

Northline’s pages use the shared sign-on kit through this site’s server. The site supplies its brand and content; the kit owns account screens and actions.

The request path

  1. Open a Northline account page.
  2. Northline’s server passes the request to the kit.
  3. The kit calls the identity service from the server.
  4. The response returns on Northline’s own page.

There is no account popup, embedded frame, or browser redirect to a provider page.

Attach a registered site

  1. Register the site, allowed routes, brand, two headless clients and active platform tenant.
  2. Choose the site-domain email mode or shared-address email mode. Both use the site’s name, wording and links.
  3. Complete the ownership and applicable sender checks, then export the registration file.
  4. Link the shared kit, load the exported file and supply the named secrets to the server environment.
  5. Pass account requests to the kit, and check the shared session before returning member content.
  6. Run every account journey in both email modes, including received mail and sessions on another site.

What belongs where

Northline owns these public pages, its theme and the member content. The shared kit owns registration, sign-in, recovery, account settings and session checks. The registration and mail services own activation and delivery.

Current attachment status

The content, the bridge and the links to every account screen are built. The shared kit now serves invitation codes, reset-only recovery and email change as well as sign-up, sign-in, recovery, password change and sign-out. Account journeys still need the registered site file, server secrets and a running provider, and none has been run yet.

The source README contains exact local run steps and the full journey coverage record. A shorter page for owners is About this demo.