Admin console
The console is where you run Odudu with a mouse. You sign in, pick a tenant, and manage its people, applications, keys and settings from one menu. Everything it does goes through the same admin API your scripts can call, so a change made here is checked and recorded exactly as one made there.
The console signs an administrator in through the same flow your users meet, and keeps the tokens on the server. The browser holds a session cookie and nothing else. Every change an administrator makes is checked against the version they read and recorded in the audit trail.
Start with the tour
A first visit takes ten minutes. You sign in, enter a tenant, find your way around the menu, look at one person and see the change that made them recorded in the audit trail.
Then pick the area you need
Each page below does one job. It says what the area is for, walks through the common tasks in order, names the actions that cannot be undone, and ends with how to do the same through the API.
- Overview: what needs attention, and the tenant's addresses.
Identity
- Subjects: the people, services and agents that sign in.
- Groups: sets of subjects that share roles.
- Roles: the names that tokens carry, and what holds them.
Applications
- Clients: the applications that sign people in.
- Scopes: what an application can ask to be let do.
- Registration tokens: let an application register itself.
Security
- Sign-in flow: what a person is asked, and in what order.
- Signing keys: rotate the keys that sign tokens.
- Sessions: see who is signed in and end it.
Tenant
- Settings: lifetimes, password rules, lockouts and retention.
- Email: the relay that sends verification and reset mail.
Observe
- Audit trail: every change and every refusal.
System
For an administrator of the system tenant only.
- Tenants: create, export, import, disable and delete a tenant. The Export entry of the menu is on this page too.
- System administrators: who can reach every tenant.
When you need the exact request
The Console paths transcripts record every route the console uses, with the real output. An admin signs in and changes a user follows one administrator from sign-in to a change.