External Integration
What This Is
Guidance for third-party apps consuming Lovelace Identity.
Who This Is For
Independent products and partner applications.
What You Will Finish With
- Correct relying-party client registration model.
- Correct environment and verification setup.
- Clear ownership boundaries between app and Accounts service.
Client Registration Model
Lovelace Accounts identifies your app by registered client_id.
- You own one or more clients in Developer Console.
- Each client defines allowed origins and redirect URIs.
- Tokens are verified against issuer and audience (
aud == client_id).
Required Configuration
bash
NEXT_PUBLIC_LOVELACE_OAUTH_CLIENT_ID=<registered-client-id>
Optional overrides:
bash
NEXT_PUBLIC_ACCOUNTS_APP_URL=https://accounts.uselovelace.com
ACCOUNTS_SERVICE_URL=https://accounts.uselovelace.com
JWT_ISSUER=https://accounts.uselovelace.com
Integration Boundary
- Lovelace Accounts Service: token issuance and client policy.
- Your app server: token verification and app session creation.
- Your UI: sign-in and auth-state controls via SDK hooks.