10.7.3 Release Notes

HYPR 10.7.3 is a patch to the 10.7.1 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.

Minimum Supported Versions

Release Date	HYPR Product	Minimum Requirement	Notes
February 19	HYPR Passwordless for Windows 10.7.3	Windows (10 "2004", 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 their respective offshoots
January 7	HYPR Passwordless for Mac 10.7.0	macOS (High Sierra, Mojave, Catalina, Big Sur, Monterey, Ventura, Sonoma 14.1 [not 14.0], Sequoia, Tahoe)	Security Key Support for YubiKey 5 Series with firmware 5.X and Feitian ePass K9 Plus, K40 Plus and their respective offshoots
January 7	HYPR Mobile App for Android 10.7.0	Android 9.0+
January 7	HYPR Mobile App for iOS 10.7.0	iOS 12.4+
February 19	HYPR Server 10.7.3	Java Development Kit (JDK) 17	Upgrade to 7.10 required before upgrading to 8.0.0 or higher
February 5	HYPR SDK for Android 10.7.1	Android 9.0+
January 7	HYPR SDK for iOS 10.7.0	iOS 12.4+
February 19	HYPR SDK for Java 10.7.3	Java Development Kit (JDK) 17+

Backward Compatibility

All HYPR components are fully compatible across the three previous/subsequent minor (X.X) HYPR releases.

Breaking Changes

• [Control Center] FIDO2 MDS legacy APIs deprecation — with the introduction of granular AAGUID allow/deny controls, legacy metadata management APIs are scheduled to be deprecated beginning in 11.3. Update integrations to the new controls under cc/api/rp/api.

Enhancements

• [Enterprise Passkey] Security hardening for passkey-based authentication workflows, improving resilience against misuse of passkey material and tightening internal validation paths.

Bug Fixes

• [HYPR Passwordless for Windows] Fixed the securityKeyTouchPolicy setting in HYPR.JSON so that touch-policy behavior is now correctly enforced in 10.7.3, aligning with the behavior that will be introduced in 11.1.0.

• [Control Center] Ensured the session table is updated with the correct FIDO user when registrations are removed and re-created, so active sessions consistently reflect the current username.

Events

See Event Descriptions for a list of all HYPR Events and parameters.

Error Messages

The following error codes have been added:

• 1207022: CONTENT_CUSTOMIZATION_INVALID_SCREEN_CONTENT — Screen content payload is invalid for the given screen name. Ensure the request body is valid JSON and matches the schema for the screen (for example, instructionsScreen, otpScreen).

To see all HYPR errors by component, see HYPR Error Codes Troubleshooting Table.

APIs

You can find detailed descriptors of these and other API calls in HYPR's full Postman API set here.

Known Issues

• [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] 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 - OneLogin] Users who are already enrolled may also be listed in the integration's User Directory, accessible through the User Management interface in Control Center.