Using the dashboard
Applications
Registering an app that signs users in through Identise: its ID, URLs, API keys, theme and tenants.
In a workspace, Applications → Create App registers something that will sign users in through Identise.
| Type | For |
|---|---|
| Standard | A normal web or mobile app. |
| Platform | A product that hosts other people's apps (a website builder, say) and creates a Tenant app per customer. See Platforms and tenant apps. |
Client Credentials
The Client ID identifies your application. Your developers put it in their configuration; the API calls it appId.
Basic Settings
The name, description and Homepage URL, your app's address. After a browser sign-in, Identise may return users to any page under it.
Security URLs
The exact callback URLs Identise may send users back to after signing in with Google, one per line. Identise refuses to send anyone, or their sign-in token, to an address that isn't listed here. In short:
https://addresses only (http://just forlocalhostwhile developing);- no passwords in the URL, no
#fragmentsand no*wildcards; - at most 20. The form tells you which line isn't allowed.
The full rules are in Callback URL rules.
API Keys
- Generate Key creates a key for your server. It's shown once: copy it into your secret store before closing the dialog.
- Rotate replaces a key, Revoke stops it working, and delete removes it. Up to 5 keys can be active per app.
Hosted UI Theme
A logo, colours and font for hosted sign-in pages.
Token Lifespans
How long your app's access tokens (5 to 60 minutes, 15 unless you change it) and refresh tokens (1 to 365 days, 30 unless you change it) last. A change applies to tokens issued from then on. A limit on sessions per user can be set through the API for tenant apps (the oldest sessions are signed out when a user goes over it).
Tenant Applications
On a Platform app, Spawn Tenant creates a customer's app from the dashboard, and the list shows the ones created through the API.