- 21 May 2026
- 12 Minutes to read
- Print
- DarkLight
- PDF
Upcoming Releases
- Updated on 21 May 2026
- 12 Minutes to read
- Print
- DarkLight
- PDF
IMPORTANT INFORMATION ABOUT THESE PRE-RELEASE NOTES
These are pre-release notes and are subject to change
Release notes are not considered final until the close of business on the date of release
This article will be updated with features, functionality, and bug fixes as our development continues
If you have any questions about these features or want to request a more in-depth discussion about the best way to leverage them, then reach out to us at productmanagement@axiad.com
May 2026
The availability date for the Browser Extension depends on the browser vendor review process, once the browser extension is available it will be moved to the release section.
Conductor Browser Extension 1.9.0
Prerequisites
Axiad Conductor UCMS 4.31 or later (for Virtual Smart Card minimum PIN length below 8 characters)
Axiad Conductor OS Bridge 1.9.0 or later (for Virtual Smart Card minimum PIN length below 8 characters)
Enhancements
PM-16556 / PM-16557 – Support for Virtual Smart Card minimum PIN lengths of 6 or 7 characters. Aligned with the Windows OS Bridge, the macOS OS Bridge now supports Virtual Smart Card profiles configured for PINs as short as 6 characters in Conductor (UCMS 4.31 or later).
June 5th 2026
Conductor HI
UCMS 4.32.1, UP 2.27.1
Features
Synchronous user status, multi-identity, and credential lifecycle
PM-17245 – Automated Credential Enforcement on User Status
Conductor now automatically suspends or revokes all credentials and associated devices when a user is disabled or deleted in the authoritative identity source. Administrators can configure per-status and per-credential-type actions (suspend, revoke, no action), set retry behavior for transient failures, and optionally notify the affected user. All enforcement events — including the previous and new state, triggering source, and any failures or retries — are written to the audit log. Enforcement is applied within minutes of the upstream status change, replacing the manual processes previously required to keep credential state aligned with identity source state.
PM-18510 – Issue Multiple Identities to a Single Device Using Alternate User Attributes
Certificate workflows can now issue multiple identities onto a single device by drawing certificate attributes from an alternate ("subsidiary") user record in addition to the current user. Administrators define alternate-user aliases on a User Source (each alias specifies a base attribute and a regular expression used to derive the subsidiary identifier at runtime), then reference them in certificate step templates using {<alias>.<attribute>} placeholders alongside the existing {user.<attribute>} syntax. Placeholders are supported in Subject DN, SAN, and Custom SID fields. References are validated at workflow save time and resolved at issuance time; if any subsidiary lookup or attribute resolution fails for a given run, the certificate step fails without partially issuing certificates, preserving consistency across the device's slots.
PM-18622 – Expired Credential Status and Per-Slot Revoke Options
Credentials and devices now reflect an "Expired" status that is evaluated dynamically based on their certificate expiration dates, providing a more accurate view of credential validity in the Unified Portal and in revoke decision logic. Credential workflows also expose two new per-PKI-slot configuration options — Revoke when expired and Revoke on update — that let administrators tailor revocation behavior for each slot. Default values preserve existing behavior for legacy workflows while applying the safer, more explicit defaults to newly created workflows.
Role management
PM-16894 – Dynamic Role Management with Fine-Grained Access Control
The Axiad Conductor Role Management framework now supports fine-grained access control with dynamic, rule-based role assignment and context-aware scoping using attribute-driven logic. Administrators can define Role Mapping Rules (which users receive a given role, based on SCIM attributes, directory attributes, or group membership), Scope Rules (which users an operator role grants access to manage), and Priority values that control evaluation order when multiple rules apply. Key capabilities include logical AND/OR operators for complex rule criteria, automatic rule evaluation at login for real-time role and scope assignment, manual assignments that override rule-based assignments, and an updated permission model that prevents self-privileged actions.
FIPS 140-3 Level 3 HSM support
PM-18624 – FIPS 140-3 Level 3 HSM Support for Thales IDPrime MD 830/MD831 and Virtual Smart Card Operations
Axiad Conductor now supports FIPS 140-3 Level 3 Hardware Security Modules for Thales IDPrime MD 830/MD831 and Virtual Smart Card credential flows. Legacy 3DES/TDES cryptographic operations have been eliminated and replaced with AES-based key derivation, bringing these card types into compliance with current FIPS standards. Existing Thales IDPrime MD 830/MD831 and Virtual Smart Card devices remain fully operational through a backward-compatible fallback mechanism. New Virtual Smart Cards use AES-based key derivation and are fully FIPS 140-3 compliant. Thales IDPrime MD 830/MD831 hardware does not support AES, so issuance of new cards of this type will no longer be supported after the migration is complete.
Device identification and PIN
PM-18314 – Globally Unique Card Identification (CUUID) for IDEMIA OCSv8
IDEMIA OCSv8 cards can now be identified using CUUID (a globally unique identifier per physical card) instead of the legacy CUID derived from CPLC. Because CUID is not guaranteed to be unique across cards, customers issuing IDEMIA OCSv8 at scale could occasionally encounter collisions during enrollment; CUUID eliminates this class of issue. A new Legacy Unique Identifier (CUID) checkbox has been added to the OCSv8 Credential Profile configuration: existing Credential Profiles have it checked by default (legacy CUID behavior preserved); new OCSv8 Credential Profiles have it unchecked by default (new enrollments use CUUID). The toggle is one-way — once a Credential Profile is saved in CUUID mode it cannot be reverted to legacy CUID mode. When CUUID mode is enabled, card-present interactions perform CUUID-first resolution with CUID fallback to preserve compatibility with existing inventory.
PM-16556 – Virtual Smart Card 6-Character Minimum PIN
The Virtual Smart Card (VSC) Credential Profile now supports a minimum PIN length of 6 characters (previously restricted to 8), aligning VSC PIN policy with other device types and supporting Windows compatibility scenarios.
Prerequisites: Conductor OS Bridge v1.9.0 or later and Conductor Browser Extension v1.9.0 or later. Both components must be upgraded for 6-digit PIN issuance to work end-to-end. Existing Credential Profiles configured with PIN length 8 or above are unaffected.
Identity verification, account recovery, and Axiad Confirm
PM-16451 – Secure, Privacy-Preserving Self-Service Account Recovery
A public, unauthenticated recovery entry point allows users to securely initiate account recovery without revealing whether an account exists. Users submit a configured identifier and, if valid, receive an email that triggers a standard Axiad Confirm identity verification flow. The experience is intentionally privacy-preserving: the same response is shown regardless of identifier validity, preventing account enumeration. Upon successful verification, users can recover access through administrator-defined mechanisms (such as temporary access credentials or password resets), with all expiration, retry limits, and verification rules enforced by existing Confirm configurations.
PM-16470 – Active Directory Parity for Axiad Confirm
Axiad Confirm now supports Active Directory as a first-class identity source, achieving functional parity with Entra ID where technically feasible. Administrators can configure AD as a direct datasource integration, map attributes, and use AD-sourced users across Confirm onboarding, verification, and recovery workflows. Where permitted, workflows can generate Temporary Access Passes for Entra-synced users and reset Active Directory passwords, including enforcing password policy and "change at next logon" behavior.
PM-16463 – Help Desk Visibility and Control Over Identity Verification State
Help Desk operators now have actionable visibility into a user's identity verification (IDV) status directly from the Unified Portal's User Details page. Operators can view current IDV state, initiation and completion timestamps, and — based on permissions — take controlled actions such as initiating verification, reconfirming identity, or deleting confirmation data. All actions are fully audited.
PM-16459 – Workflow-Driven Identity Verification Outcomes in Conductor
Conductor workflows can now natively incorporate Axiad Confirm with configurable post-verification outcomes, turning identity verification into an enforceable, reusable workflow primitive rather than a one-off step. Administrators can enable Confirm per workflow, define success/failure messaging, and configure post-verification actions such as generating Temporary Access Credentials or issuing initial Active Directory passwords. These actions can be combined and tailored per workflow type, allowing identity verification to directly drive secure onboarding, recovery, and access enablement.
Enhancements
PM-18626 – Safe Expiration Defaults Enforced During Database Upgrade
The UCMS database upgrade now systematically aligns all existing credential workflows to safe expiration defaults — CARD_VALID_MONTHS is set to NULL and SKIP_EXPIRED_CARD_REVOCATION is set to Y — to prevent unintended device expirations or revocations following an upgrade. The previous and new values are written to a per-workflow audit record so administrators can review and, if needed, adjust the configuration after the upgrade. This change does not require any manual action.
PM-17945 – Always Redirect to IdP on Expired SSO Session
When a user's SSO session expires inside the Unified Portal, UP now consistently redirects them to the configured Identity Provider for re-authentication and returns them to the screen they were on. This applies to GET, POST, PATCH, and GraphQL calls (including credential search), removing prior cases where an expired session surfaced as an error or stale state instead of a clean re-auth.
PM-19136 – Configurable Master Key for Virtual Smart Card Offline PUK Generation
The Virtual Smart Card (VSC) Credential Profile now exposes a new Offline unlock key option that controls which master customer-admin key is used to generate the PUK for the offline unlock challenge/response flow. The option is only presented and applied when both a TDES master customer-admin key and an AES master customer-admin key are configured on the Credential Profile, and accepts two values: AES (default, preserves existing behavior) and TDES (uses the TDES-derived customer-admin key to generate the PUK). Credential Profiles configured with only one master key are unaffected, and existing Credential Profiles continue to behave as before until the new option is set.
PM-17425 – Default Country Fallback for Identity Verification
A new Default Country field has been added to the Verification Server configuration (Configuration > Verification Server). Administrators can define an organization-wide fallback country using a 3-letter ISO 3166-1 alpha-3 country code (e.g., USA, GBR, DEU), eliminating identity verification failures for users who are missing a country attribute in their profile.
PM-17220 – Branding-Based Table Column Visibility
The Unified Portal now supports configuring default table column visibility through branding.json. Administrators can define which columns are shown or hidden by default for each table across the portal, enabling a tailored interface experience aligned with organizational preferences.
PM-16181 – Selective SID/Custom SID per Certificate Type
It is now possible to configure, for each certificate type, whether to include the SID X.509 extension, which directory/SCIM attribute to use for its value, and whether that attribute is mandatory or optional.
Bug Fixes
Identity and access management
PM-18304 – LDAP Synchronization Failure Due to Duplicate User Identifier.
Resolved an issue where LDAP synchronization could fail with a unique-constraint violation on the user identifier column. Duplicate-identifier scenarios are now handled gracefully and synchronization completes as expected.
PM-19113 – Batch LDAP Membership Query Failure on Microsoft SQL Server.
Resolved an issue where the batch LDAP membership query could fail on Microsoft SQL Server because of incorrect recursive-query syntax. The query has been adjusted to use SQL Server–compatible recursive CTE syntax.
PM-19112 – SAML Redirect Loop for a Non-Existent User.
Resolved an issue where a SAML authentication request for a user that did not exist in Conductor could trigger a continuous redirect loop, eventually producing a "Bad Request — Header Too Long" error. Unknown users are now handled cleanly without an authentication loop.
Credential issuance and workflows
PM-19080 – Credential Issuance Failed with an Internal Error.
Resolved an issue where credential issuance could fail with an internal null-pointer error under specific workflow configurations.
PM-16832 – Intermittent Null-Pointer Error During Certificate Issuance.
Resolved an intermittent problem which previously led to null-pointer errors during certificate issuance.
PM-19145 – Device Lifecycle Setting Ignored for Key-Management Certificates When User is Disabled.
Resolved an issue where the Skip Device Life Cycle configuration was not honored for Key Management certificates when the associated user was disabled. The setting is now respected for all certificate types.
PM-19146 – Device and Certificate States Not Updated When the CA Was Unreachable.
Resolved an issue where device and certificate states were not refreshed when the certificate authority was temporarily unreachable. State is now reconciled once connectivity is restored.
PM-19114 – Credential Workflow Page Stuck Loading After an Authorization Error.
Resolved an issue where the Credential Workflow page could remain in a perpetual loading state when the underlying request returned an authorization error. The page now surfaces the error and recovers cleanly.
PM-19382 – Workflow Cloning Failed With an Authorization Error.
Resolved an issue where cloning a credential workflow could leave the page in a loading state because of an authorization error. Workflow cloning now completes successfully.
PM-19172 – Credential Profile Creation Page Failed to Load.
Resolved an issue where the Credential Profile creation page could fail to load with a view-expired error after a period of inactivity.
PM-19109 – EJBCA Credential Server Authority ID Not Preserved.
Resolved an issue where the Authority ID value was not preserved when editing an EJBCA Credential Server configuration, and could appear pre-populated when creating a new EJBCA Credential Server. The Authority ID now persists exactly as entered and is empty by default for new configurations.
PM-16667 – PIN Length Exceeded Policy Maximum.
Resolved an issue where users could enter PINs exceeding the maximum length defined in the PIN Policy, causing verification failures.
PM-18041 – Axiad ID iOS Credential Profile Save Error.
Resolved an issue where the Axiad ID iOS Credential Profile could not be saved because a permission validation failure and a duplicate name conflict occurred simultaneously.
FIDO2 / Passkey
PM-17674 – FIDO2 Credential Issuance Reported a Spurious Error.
Resolved an issue where FIDO2 credential issuance failed with the error "The Identity Provider was unable to process the request," preventing the credential from appearing under the user's identities even when the underlying registration in Entra ID had completed.
PM-17596 – FIDO2 / Passkey Registration Reported a Spurious Error.
Resolved an issue where FIDO2 / Passkey registration failed with the error "The Identity Provider was unable to process the request," even when the passkey was successfully registered in Entra ID. The credential was not being reflected in the My Identities view.
Cards
PM-15972 – IDEMIA Legible ID Mismatch on Enrollment.
Resolved an IDEMIA Legible ID mismatch that caused enrollment failures.
Notifications
PM-19119 – Enforcement Notification Email Not Sent for LDAP-Disabled Users.
Resolved an issue where the enforcement notification email was not delivered for users disabled in LDAP. Notifications are now sent consistently for all configured user status changes.
PM-19163 – Enforcement Notification Email Used the Wrong User-Name Placeholder.
Resolved an issue where the enforcement notification email greeting included the literal placeholder %username% instead of resolving the recipient's first name.
PM-19164 – Enforcement Notification Email Sent for Deleted Users.
Resolved an issue where the enforcement notification email was sent to users whose accounts had been deleted. Notifications are now suppressed for deleted users.
Portal and Help Desk
PM-17150 – Refreshing the Unified Portal Returned a Forbidden Error.
Resolved an issue where refreshing the Help Desk page incorrectly showed a "Forbidden" error. The page now reloads smoothly and works as expected.
PM-17153 – Help Desk Portal Missing or Unexpected UI Elements.
Resolved an issue in the Help Desk Portal where some expected UI elements were missing and others appeared unexpectedly. The page now displays clearly and works as intended.
Operational
PM-17995 – Excessive Temporary Database Storage Consumption During Cleanup.
Resolved an issue where an internal cleanup query could consume excessive temporary database storage on Microsoft SQL Server, occasionally degrading performance under sustained load. The query has been rewritten to bound its working set.
PM-17866 – Internal Logging Component Upgrade.
Upgraded the internal logging component to a newer, more secure version. This update strengthens overall system security and helps protect customers.
Security Fixes
Platform Security Improvements. As part of this release, Axiad has addressed several security vulnerabilities across the Axiad Conductor platform identified through routine third-party dependency scanning.
PM-19063 – Addressed vulnerabilities: CVE-2026-42587, CVE-2026-42579, CVE-2026-42583.
PM-19158 / PM-19159 – Addressed vulnerability: CVE-2026-41284.
PM-19323 – Addressed vulnerability: CVE-2026-44503.
PM-18471 / PM-18450 – Addressed vulnerabilities: CVE-2026-29145, CVE-2026-34500, CVE-2026-29129, CVE-2026-24880.
PM-18084 / PM-18085 – Addressed vulnerability: CVE-2026-22733.
PM-18825 – Addressed vulnerabilities: CVE-2026-34478, CVE-2026-40973, CVE-2026-34480.
PM-18478 – Addressed vulnerabilities: CVE-2026-40477, CVE-2026-2332.
PM-18269 – Addressed vulnerability: CVE-2026-4800.
PM-18206 – Addressed vulnerability: CVE-2025-8671.
PM-18145 – Addressed vulnerability: CVE-2026-22732.
PM-18826 – Addressed vulnerability: CVE-2026-34477.
PM-18083 – Addressed vulnerability: CVE-2026-22737.
PM-18128 – Addressed vulnerability: CVE-2026-33871.
PM-16661 – Addressed vulnerability: CVE-2025-12383.
PM-18951, PM-18205, PM-18268 – Upgraded additional dependencies to address issues identified through routine security scanning for which CVE identifiers had not yet been assigned at the time of release.
Known Limitations
PM-18472 – Credential issuance using YubiKey 4 with IdenTrust CA fails during the certificate import phase. The CSR is generated and submitted successfully, but the process fails with an error indicating the CSR/PKCS#10 is invalid and the certificate cannot be imported. YubiKey 5 and YubiKey 5.7.1 devices are not affected.