Skip to main content
Product updates for TruU IDV, newest first. Each entry groups changes by area and links to the updated page.

November 2026

ServiceNow
  • ServiceNow app 1.1.3 authenticates event delivery with OAuth 2.0 client credentials instead of a shared secret. Connect creates a web-service-only integration user and an OAuth client, and the app’s events endpoint now requires authentication and an ACL role. Reconnect after upgrading. See How TruU authenticates to your instance.
  • The console’s manual ServiceNow setup is replaced by the bare linking code, which you can paste on the app’s Connect to TruU page when the link can’t be opened.

October 2026

Use cases replace policies
  • Routing now lives on use cases. Each use case (Onboarding, Credential reset, Helpdesk, Verification, or your own) sets the wording people see, which flow each directory group gets, and what happens after success. The Policies page is gone. See How use cases work.
Directories and sign-in
  • Okta joins Microsoft Entra ID as a directory. See Connect Okta.
  • Console sign-in adds passkeys, and enterprise SSO supports Microsoft Entra ID, Google, Okta, PingFederate, PingOne and any OIDC provider, with passkey recovery for Owners. See Sign-in, SSO and passkeys.
  • One account can belong to several workspaces. See Workspaces.
Connectors
  • Microsoft Teams: agents send verifications from Teams chat. See Microsoft Teams.
  • One-click setup from TruU Passwordless creates a workspace, shares the Entra ID directory and seeds an enrollment flow. See TruU Passwordless.
Setup
  • A first-run tour and setup templates get a workspace to a working flow in minutes, and the setup review checks factors, flows and use cases against your real directory before go-live. See Quickstart and Go live.
  • Storage supports several named stores with Read and Write access. See Storage.

July 2026

Request lifecycle
  • Verification requests gain a cancelled status. Agents can cancel an open request from the Help Desk Console or with POST /helpdesk/requests/{request_id}/cancel.
  • A new API error code accompanies the status: REQUEST_CANCELLED. See Errors.
ServiceNow
  • The ServiceNow connector is available: verify callers directly from incident records, and receive every verification lifecycle event back as incident work notes with a status field update.
  • Setup uses a single-use linking code, so the ServiceNow app provisions its own credentials with no copy-paste. Test connection, key rotation, and secret rotation are built in. See ServiceNow.
Partner links API
  • POST /integrations/links creates a verification request, delivers the link by email, SMS, or return value, and responds with the short URL and expiry: one call to wire verification into any ITSM or portal. See Link creation.
Self-service portal
  • End users can request their own verification link from a workspace portal: they enter their work email, pick a masked delivery channel, and receive a link, without an agent in the loop. The portal is rate-limited and delivers only to directory-known channels. See Self-service portal.
Microsoft Entra ID Branding
  • White-label the end-user experience: logo, colors with contrast checks, brand panel styles, headline, and trust bullets, with live preview. Desktop layouts add a branded trust panel. See Branding.
Credential health
  • Settings → Credential health monitors the status of connected credentials and connectors (directory, storage, ServiceNow, and more), with an on-demand sync and API access via the idv:credential_health:read and idv:credential_health:sync scopes. See Credential health.
Windows TAP and PingOne MFA
  • Policies gain “After success” actions: issue a Microsoft Entra Temporary Access Pass, or reset a user’s PingOne MFA devices, automatically when verification succeeds. See Windows TAP and PingOne MFA reset.
  • PingOne Verify is available as a proofing provider alongside the integrated provider and Persona. See Proofing providers.
Factors
  • One-time code factors gain resend budgets with a visible cooldown countdown, configurable per factor. The SMS factor asks the user to confirm the last four digits of their phone number instead of displaying a masked number.
  • The Face factor’s reference image resolves through a configurable source list and can reuse the photo captured during document proofing.
  • TOTP authenticator setup is a post-verification re-enrollment step rather than a verification factor.
Link lifetimes
  • Link lifetime depends on purpose: 30 minutes for help desk, 60 minutes for reset, 7 days for onboarding. Requesting a link for a user and purpose with one already active reuses the active link and resets its expiry. See Verification requests.