Your values Fill in your own to see them in every example
The part after /o/ in your hub’s address.
That doesn’t look right yet. For example: a1B2c3D4e5F6
On the app’s page in the hub, under Credentials.
That doesn’t look right yet. For example: q3Jx8vN2mZ0bT5sLwK7yHc4dR1fGaE9uPiO6nVjXkMs
Client secret stays a marked placeholder here, never filled in: the hub gives you secrets, and only your server should hold them.
Saved in this browser only, for every page of these docs. Nothing you type leaves this page.
Do this once, in the Trustaige hub, as an administrator of your organization.
-
Prove your domain. In Domains, add a DNS record. Credentials you issue carry the domain you proved, so people can see they are yours.
-
Turn on issuing and design one credential. In Customers → Overview, choose Turn on issuing, then Design a credential. Start from Customer account: it lasts while they’re your customer and renews on its own. Leave who can get it as People you offer it to.
-
Connect your app. In Customers → Overview, choose Connect your app: the new-application flow opens with Customers chosen. Admit your credential. Add your callback URL as a redirect URI, your home page as a post-logout URI, and your sign-in route as the initiate login URI. Note its client ID and secret.
-
Register your site for HumanProof. In HumanProof → Sites, add your site’s host. Your sign-up form can then ask a visitor to prove they are a person, without learning who. See HumanProof.
One app does both halves
Your customers sign in through the app you connected, and your server calls the hub with the same client to offer, read and end the credentials it admits. For those calls a Customers app always holds three scopes, which come with the app: there’s nothing to set up or grant, and you only choose which to request on a token.
| Scope | Lets your server |
|---|---|
offers:write | Offer a credential: create a subject and a claim link |
issued:read | Read your credential types and the subjects you created |
issued:manage | Erase a subject |
Its calls are named as the app in your organization’s audit log, and what it
creates is its own: a subject it minted is invisible to any other app in your
organization, which reads it as 404.
Your four values
The credential type’s name is the one you entered when you designed it.
Customer below is an example, not a reserved name: names are unique within
your organization and permanent, and yours must match exactly.
TRUSTAIGE_ISSUER=https://id.trustaige.com/o/<your-org-id>
TRUSTAIGE_CLIENT_ID=<your-client-id>
TRUSTAIGE_CLIENT_SECRET=<your-client-secret>
TRUSTAIGE_CREDENTIAL_TYPE=Customer
Next: sign people up.
TRUSTAIGE_ISSUER=https://id.trustaige.com/o/<your-org-id>
TRUSTAIGE_CLIENT_ID=<your-client-id>
TRUSTAIGE_CLIENT_SECRET=<your-client-secret>
TRUSTAIGE_CREDENTIAL_TYPE=Customer