Auth
Auth overview
Hosted sign-in for your users, a Bearer key for your backend, policy enforced where every call passes.
Concepts
| Term | Meaning |
|---|---|
| Application | One tenant with isolated test and live environments. The console groups them as one app and lets you switch context. |
| Tenant | A customer brand you serve. Its slug is the identity every engine keys data on. Canonical spelling; permanent. |
| Client ID | Public identifier of the application. Safe to embed. |
| Client secret | Bearer credential for your backend. Shown once, stored hashed, rotatable. |
| Ticket | Single-use token delivered to your callback after hosted sign-in; exchanged server-side for the identity. |
The sign-in flow
- 1
Redirect
Your app sends the user to DevSewa hosted sign-in for the application. - 2
Authenticate
DevSewa handles password, e-mail verification and MFA under your policy. - 3
Return
The browser is redirected to one of your allow-listed callback URLs with a one-time ticket. - 4
Exchange
Your backend callsPOST /v1/auth/exchangewith its client secret and receives the verified identity.