Choosing an Integration
This section covers all three:
- No-code Dashboard - nothing to build
- OAuth OIDC - the typical way to go
- REST APIs - for the complex and the long-running
Which integration is right for you?
Find the line closest to what you need.
| Where to start | What you need |
|---|---|
| No-code Dashboard | I just need to verify IDs from time to time |
| No-code Dashboard | We need to verify lots of IDs for regulatory compliance, and want secure storage |
| No-code Dashboard | We must ensure people have certain credentials before we do business with them |
| OAuth OIDC | We need to verify IDs, and grant access to an area of our website or portal |
| OAuth OIDC | Access to our systems should be secured by the latest biometric technology |
| OAuth OIDC | We need to guarantee we can prevent bots signing up to our services |
| OAuth OIDC | Ensuring banned or blocked users can never rejoin our community is critical |
| REST APIs | We need an asynchronous integration, to allow a third party plugin to make requests |
| REST APIs | We require sharing of credentials that may take a while to obtain, such as background checks |
| REST APIs | We need to issue credentials to an individual, and be able to access the verified credential or source file at any time |
| Any of the above | We need to offload the risk of ID document checking and storage |
No-code Dashboard
No integration required.
Get started in seconds by simply logging in to your account at https://dashboard.truevault.com.au and following the simple prompts and intuitive navigation.
This is also a good way to road test what we do before committing dev time to an integration.
Complexity: Super simple! Anyone can do it.
OAuth OIDC
This is the typical way to go.
This gives you "Continue with Google" style authentication and session functionality, but with a few massive added benefits, including:
- Ensuring an individual can only ever sign up once (no more free-trial abuse or ban circumvention)
- Ensuring all users have verified their identity at source (no more identity fraud)
- Guaranteeing bots can't sign up (no more spam)
- Adding biometric authentication to your authentication flows (no more phishing or stolen device attacks)
- Automatically requiring biometric 3FA (face + phone + mobile) when sessions expire (no more custom workflows to build)
- Collect pre-verified required ID verification components during the same single sign-up workflow (no more manual ID collection or storage)
Complexity: Medium. May be achieved using off-the-shelf OAuth OIDC plugins, as long as you can add custom claims.
REST APIs
For complex, long running, or asynchronous integrations.
The credential API may be combined with an OAuth OIDC Flow to issue bespoke Verifiable Credentials to an individual, after a single, unbroken onboarding experience.
Complexity: Pretty tricky, but simple enough for a decent developer.