Skip to main content
This page is for the Owner or Admin who keeps the workspace running. When you finish you will know what is checked, how often, and where to rotate each credential. TruU IDV depends on credentials you control: the directory app secret, connector keys, storage access. When one expires, nothing announces it; verifications start failing for users until someone traces it back to a dead secret. Settings → Credential health checks those credentials so you find out first.

What it checks

The health grid

Each credential is a row showing its status (for example Healthy, Unknown, or Not probed), when it was last checked, its expiry if known, and a Manage link. Healthy cards confirm at a glance that dependencies are sound; an expiring or failing card names the connection and where to fix it.
Treat an expiring directory secret as urgent. Directory access underpins use case rules and most factors, so a lapsed directory secret stops verification for everyone, not one feature.

Cadence

  • Daily sweep. Every credential is checked once a day.
  • Sync now. Trigger a check on demand, for example right after rotating a secret. The request is accepted immediately and cards update as checks complete. Repeated clicks within a short window are coalesced into one run.
  • At connect time. The same checks run when you first connect a directory, connector, or store.
  • Email alerts. When a credential is about to expire or its status gets worse, the workspace’s primary admin email (the address that created the workspace) is notified.

API access

Monitoring systems can read the same data through the TruU IDV API:
  • GET /admin/credential-health returns the status of every checked credential. Scope idv:credential_health:read.
  • POST /admin/credential-health/sync triggers a refresh and returns 202 Accepted. Scope idv:credential_health:sync.
Create a client and grant scopes under Settings → API clients. See API authentication.

Gotchas

  • ServiceNow probe fails after a change in ServiceNow. The TruU Identity Verification OAuth client or the truu.idv.integration user was deactivated, deleted or given a new secret in your instance. Generate a new connect link and connect again; see ServiceNow.
  • Directory card shows a permission failure on one check only. Usually Organization.Read.All without consent. Grant consent in the Entra admin center and run Sync now.
  • Storage card fails right after you added a store. The credential or bucket policy does not grant the role you chose (read or write). Re-test from Settings → Storage.