10.3.4 Release Notes
HYPR 10.3.4 is a patch to the 10.3.0 Enterprise Channel Release.
The Enterprise Release Channel follows a quarterly upgrade cycle, ensuring a stable and predictable update process. This schedule provides organizations with ample time to test, adapt, and implement changes while minimizing disruptions to business operations. With each release, customers receive the latest security, performance, and feature enhancements, allowing them to stay up to date with improvements while maintaining operational stability.
To enable our customers to be more proactive in anticipating industry changes that affect HYPR architecture and topology needs, we have created the Breaking Changes section of the Release Notes. This section may be updated after the GA Release as information becomes available to HYPR.
Minimum Supported Versions
Release Date | HYPR Product | Minimum Requirement | Notes |
---|---|---|---|
June 25, 2025 | HYPR Passwordless for Windows 10.3.0 | Windows (10 "1803", 11) | Reboot required if upgrading from 7.6 or below; Security Key Support for YubiKey 5 Series with firmware 5.X, YubiKey Bio Multi-Protocol Edition, IDEMIA ID-One on Cosmo 8.2, Feitian K9 Plus and K40 Plus and its offshoots |
July 18, 2025 | HYPR Passwordless for Mac 10.3.1 | macOS (High Sierra, Mojave, Catalina, Big Sur, Monterey, Ventura, Sonoma 14.1 [not 14.0]) | Security Key Support for Yubikey 5 Series with firmware 5.X and Feitian ePass K9 Plus, K40 Plus and their respective offshoots |
June 25, 2025 | HYPR Mobile App for Android 10.3.0 | Android 9.0+ | |
July 18, 2025 | HYPR Mobile App for iOS 10.3.1 | iOS 12.4+ | |
August 20, 2025 | HYPR Server 10.3.4 | Java Development Kit (JDK) 17 | Upgrade to 7.10 required before upgrading to 8.0.0 or higher |
July 25, 2025 | HYPR SDK for Android 10.3.2 | Android 9.0+ | |
July 25, 2025 | HYPR SDK for iOS 10.3.2 | iOS 12.4+ | |
July 25, 2025 | HYPR SDK for Java 10.3.2 | Java Development Kit (JDK) 17+ |
All HYPR components are fully compatible across the three previous/subsequent minor (X.X) HYPR releases.
Enhancements
-
[Integrations] Extended code customization implementation to run prior to outcomes being issued, enabling enhanced workflow control and customization capabilities
-
[Adapt] Modified feature flag to enable policy evaluations via API while keeping event flow to S3 disabled, allowing direct API-based evaluations without unnecessary event ingestion
Events
See Event Descriptions for a list of all HYPR Events and parameters.
Error Messages
To see all HYPR errors by component, see HYPR Error Codes Troubleshooting Table.
APIs
- [Identity Verification (IDV)]
- Added
OUTCOME_API_CALL
to the available customization types in theCodeCustomizationRequest
schema, enabling code customization to run prior to outcomes being issued:POST /cc/api/idv/code-customization
POST /cc/api/idv/code-customization/update
POST /cc/api/idv/code-customization/test
- Added
otpStepStatus
field with enum values (PASS
,FAILED
,NOT_CONFIGURED
,NOT_ASSOCIATED
) to provide detailed OTP verification status:GET /cc/api/idv/helpdesk/workflows/{workflowId}
- Added
otpMedium
field with enum values (EMAIL
,SMS
) to indicate the verification method used:GET /cc/api/idv/helpdesk/workflows/{workflowId}
- Added
You can find detailed descriptors of these and other API calls in HYPR's full Postman API set here.
Bug Fixes
-
[Affirm] Fixed an issue where email verification was incorrectly labeled as "phone" in the Activity Log and Help Desk interface
-
[Affirm] Fixed an issue where liveness step failures were not properly failing the overall verification flow when using injectable outcomes
-
[Affirm] Fixed an issue where OIDC authentication was being skipped for requesters instead of prompting for authentication
-
[Affirm] Fixed an issue where an OIDC
authorization_request_not_found
error was occurring during OAuth callback processing in requester flows
Known Issues
-
[Adapt] The user is not being blocked even after an unsuccessful Monitor Authentication login attempt
-
[Adapt] Upon a cold start of the risk engine (e.g., after an upgrade) blocked policy might not be applied
-
[Authenticate] The HYPR Service does not always restart as intended after resuming from Modern Standby or hibernation, sometimes resulting in multiple restart attempts and network recovery failures
-
[Control Center] Server still sends push notifications with incorrect proxy credentials
-
[HYPR Passwordless for Windows] The text messages in the Windows login screen are replaced with incorrect text by HYPR Passwordless credential provider under certain circumstances
-
[HYPR Passwordless for Windows] HYPR displays an error when a paired Yubikey Bio MPE has the maximum number of fingerprints stored already
-
[HYPR Passwordless for Windows] If the YubiKey mini-driver is updated by HYPR Passwordless installer, a reboot is required
-
[HYPR One App for iOS] The text below the logo on the home screen still says "True Passwordless Security" and has not been updated to "Identity Assurance"
-
[HYPR One App for iOS] Registration isn't blocked and no alert is displayed when a version enforcement policy is set in Control Center for a future date
-
[Integrations - Okta] The Enroll button is displayed for Control Center admins who are not in the Okta directory
-
[Integrations - Okta] New integrations cannot be added due to 'Default Policy' errors
-
[Integrations - Okta] Users deleted from the Integrations rpApp do not get unassigned from the Okta app
-
[Integrations - Keycloak] Missing HYPR theme in local environment