Skip to main content
View as MarkdownOpen in ChatGPTOpen in Claude

Identity Mesh — June 24, 2026

Release Date: June 24, 2026
Release Type: Mixed (New Features, Improvements, Bug Fixes)

Overview​

This release delivers four features and one bug fix:

  • First-run setup for new environments — the first tenant on a fresh environment can now be created entirely through the product, with no manual setup steps.

  • Email code verification for onboarding links — onboarding links now require a 6-digit code sent to the same email address, protecting sign-up against link interception.

  • Universal REST API connector — connect any REST API that publishes an OpenAPI or Swagger specification, through a guided setup, without waiting for a purpose-built connector.

  • Correlation review workflow improvements — batch decisions on the correlation diagram, one-click quick reject, focus mode, and an always-visible save bar.

It also ships the timestamp display preference to production and fixes an audit-log view that did not follow that preference.

New features​

First-run setup for new environments​

On a brand-new environment there was previously no way to create the first tenant through the product — initial setup required manual intervention. This release adds a supported first-run setup path.

What changed:

  • When an environment has no tenants yet, the sign-in page offers a first-run setup login for the platform operator.

  • Signing in through first-run setup opens the guided onboarding experience directly, which creates the first tenant, its first administrator, and its identity provider routing.

  • First-run login works only while the environment has no tenants. Once the first tenant exists, it is rejected and normal sign-in takes over.

  • First-run sign-ins and first-tenant creation are audited, and the login is rate-limited and protected against repeated failed attempts.

Why it matters: standing up a new environment no longer requires out-of-band steps — the first customer can be onboarded entirely through the product.

Onboarding invitations are delivered as a sign-in link sent by email. Previously the link was the only factor: anyone who obtained it could complete onboarding. This release adds a second verification step.

What changed:

  • Opening an onboarding link now presents a verification screen instead of starting onboarding immediately.

  • A 6-digit code is sent to the same email address the link was issued to. The code expires after about 10 minutes.

  • Onboarding starts only after the correct code is entered. The link and code are consumed together — neither can be reused.

  • If the code expires before you enter it, you can request a new code without needing a new onboarding link.

  • After three failed code attempts, the link is invalidated — contact Axiad support or request a new onboarding link.

Why it matters: even if an onboarding link leaks — through a forwarded email, for example — it cannot be redeemed without access to the recipient's mailbox.

Universal REST API connector​

You can now connect Axiad Mesh to any REST API that publishes an OpenAPI or Swagger specification, without waiting for a purpose-built connector.

What changed:

  • A guided, conversational setup walks you through configuring the connector: application name, base URL, the OpenAPI or Swagger specification, and the authentication scheme. The setup validates the specification and helps you select which data to collect.

  • Connector configurations are versioned, so template upgrades are deliberate rather than automatic.

  • Connector activity is recorded in more detail, and authentication failures now report the specific error returned by the source system — making setup problems much easier to diagnose.

Why it matters: adding a new REST data source becomes self-service — an API specification and a short guided setup, instead of a request for a custom connector.

Timestamp display preference​

The tenant-level timestamp display preference introduced in the previous release ships to production in this cycle. See the June 17, 2026 release notes for the full description.

In summary:

  • Tenant administrators choose Browser Timezone or UTC as the tenant-wide default.

  • One standardized timestamp format applies across all interactive views.

  • CSV exports always remain UTC, regardless of the display preference.

  • Daylight saving time is handled correctly, setting changes take effect immediately, and rendering falls back safely if the setting is missing.

A follow-up fix in this release (see Bug fixes below) brings the audit-log view under Settings → Config Management in line with the preference — with it, every audit-log view now respects the tenant setting.

Correlation review workflow improvements​

The correlation review workflow on the human identity dashboard has been overhauled to reduce the time it takes to complete a correlation review session. The individual pieces shipped across recent releases; as of this release, the full set is live.

What's now available:

  • Select multiple correlation links directly in the correlation diagram using per-link checkboxes.

  • Confirm or reject each selected link inline — a single batch can mix confirmations and rejections.

  • A Save and Continue bar stays visible at the top while you scroll.

  • A persistent "Unsaved changes" banner appears while decisions are pending, and a navigation guard prevents losing them.

  • One-click quick reject saves a single rejection immediately and moves on, without saving other pending decisions.

  • Focus mode: click a node to dim unrelated nodes and links (they are not hidden). Click the same node again, or the empty canvas, to exit.

  • If some decisions in a batch fail to save, results are reported per decision so you can retry only what failed.

Why it matters: reviewing sessions with many correlation links no longer means acting on one link at a time. Batch decisions, quick reject, and focus mode together are designed to cut review session time by roughly 30 percent on representative workloads.

Improvements​

This release also includes reliability and performance improvements with no user-visible changes.

Bug fixes​

Audit-log timestamps under Settings → Config Management now follow the tenant preference​

The timestamp display preference covered most of the product, but the audit-log view under Settings → Config Management was missed: its Time column kept a hardcoded "Time (UTC)" header and the old timestamp format, and long values were cut off with no way to read them in full.

What changed:

  • The Time column now follows the tenant timestamp preference, and the column header reflects the selected time zone — UTC or your browser's local zone.

  • Values render in the standardized timestamp format used across the product.

  • Hovering over a timestamp shows the full value, so nothing is lost when the column is narrow.

Why it matters: every audit-log view now honors the tenant timestamp preference uniformly.