OAuth backend

The OAuth backend turns Everlock into an OAuth 2 and OpenID Connect issuer for applications that should trust Everlock users.

Instead of keeping a separate identity silo per app, Everlock can issue tokens from the same user registry and access model already used by its own services.

What it is for

Use the OAuth backend when you want:

• a self-hosted OAuth or OIDC provider for internal or personal applications
• one login system shared between Everlock and HTTP applications around it
• signing keys, client registrations, and issuer state stored inside Everlock

How it fits in the system

The OAuth backend owns:

• token issuance
• client registrations
• signing keys
• issuer configuration

The HTTP frontend owns browser-visible login transport and request routing.

Typical operator flow

1. enable the backend
2. configure an issuer URL and store
3. register one or more client applications
4. point those applications at Everlock discovery and token endpoints
5. let users authenticate with their Everlock accounts

Pages

• Provider model and configuration reference
• Users, groups, and access control
• Frontends

Read next

• Admin backends
• Users, groups, and access control
• Architecture