Registering OAuth clients
An application that wants to log its users in through Everlock is registered as a **client**. Registration is what produces the `client_id` and `client_secret` the application needs, and it names the
Documentation
Tag: oauth
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 to
Provider model and configuration reference
This page covers Everlock's OAuth 2 and OpenID Connect provider model. The OAuth backend runs behind `frontend-http` and uses an Everlock `versioned-storage` store for client registrations, signing ke