10.7.2 Release Notes
HYPR 10.7.2 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 5 | HYPR Passwordless for Windows 10.7.2 | 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 5 | HYPR Server 10.7.2 | 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 5 | HYPR SDK for Java 10.7.2 | Java Development Kit (JDK) 17+ |
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
-
[HYPR Passwordless for Windows] Bundled YubiKey Smart Card Minidriver 5.0.4.273 to improve compatibility in Citrix environments.
-
[Integrations - Keycloak] Improved V1 flow log clarity and consistency to support troubleshooting (including better step visibility and timeout handling).
Events
See Event Descriptions for a list of all HYPR Events and parameters.
The following Event(s) were added or updated in this release:
-
AFFIRM_WORKFLOW_ANCHOR_IMAGE— an anchor image is captured or associated with an Affirm workflow for visual verification. -
EMAIL_NOTIFICATION_SENT— an email notification was successfully sent using the configured template. -
EMAIL_CUSTOM_TEMPLATE_CREATE,EMAIL_CUSTOM_TEMPLATE_UPDATE,EMAIL_CUSTOM_TEMPLATE_DELETE— lifecycle events for creating, updating, and deleting custom email templates. -
EMAIL_CUSTOM_TEMPLATE_VERSION_CREATE,EMAIL_CUSTOM_TEMPLATE_VERSION_UPDATE,EMAIL_CUSTOM_TEMPLATE_VERSION_DELETE,EMAIL_CUSTOM_TEMPLATE_VERSION_RESTORE— lifecycle events for managing specific versions of custom email templates. -
CC_VIEW— an admin viewed Control Center content such as logs or audit data. -
EVENT_HOOK_CREATE,EVENT_HOOK_MODIFY,EVENT_HOOK_DELETE,EVENT_HOOK_READ_SENT_EVENTS— events for creating, updating, deleting, and reviewing Event Hook configurations and sent events.
Error Messages
The following error codes have been added or updated:
-
1201098:
USER_NOT_IN_SINGLE_REG_PILOT_GROUP— Single reg pilot group is enabled in Control Center. The user is not in it. This is okay if it's intentional; otherwise, add the user to the pilot group from the Control Center admin console and try again. -
1202800:
SCHEDULER_INVALID_REQUEST— Scheduler request is invalid (bad payload, invalid state, or invalid parameters). Verify request payload and parameters; check server logs for details. -
1202801:
SCHEDULER_JOB_NOT_FOUND— Requested scheduler job does not exist. Verify job id/tag/region and ensure the job is registered in this node. -
1202802:
SCHEDULER_ALREADY_EXECUTING— Job is already executing and cannot be triggered again at this time. Wait for the current execution to finish, then retry. -
1202803:
SCHEDULER_DISABLED— Job is disabled and cannot be executed. Enable the job (clear disabled state / updatedisabledUntil) and retry. -
1202804:
SCHEDULER_NOT_INITIALIZED— Scheduler is not initialized on this node (not started or misconfigured). Verify scheduler configuration and node startup logs; ensure the scheduler is enabled and running. -
1202805:
SCHEDULER_METADATA_NOT_FOUND— Static metadata for the requested job was not found. Verify the job is declared in the static metadata registry for this node/tag/region. -
1202806:
SCHEDULER_JOB_DATA_PREPARATION_FAILED— Unable to prepare job data for scheduler execution. Check scheduler job configuration and input data; inspect server logs for the root cause. -
1210000:
EMAIL_CUSTOMIZATION_NOT_FOUND— We were unable to find the email customization. Check that the provided customization ID is correct. -
1210001:
EMAIL_CUSTOMIZATION_CREATE_PROBLEM— We were unable to create the email customization. Check the error payload for details. -
1210002:
EMAIL_CUSTOMIZATION_UPDATE_PROBLEM— We were unable to update the email customization. Check the error payload for details. -
1210003:
EMAIL_CUSTOMIZATION_DELETE_PROBLEM— We were unable to delete the email customization. Check the error payload for details. -
1210004:
EMAIL_CUSTOMIZATION_VERSION_NOT_FOUND— We were unable to find the email customization version. Check that the provided version ID is correct. -
1210005:
EMAIL_CUSTOMIZATION_VERSION_CREATE_PROBLEM— We were unable to create the email customization version. Check the error payload for details. -
1210006:
EMAIL_CUSTOMIZATION_VERSION_UPDATE_PROBLEM— We were unable to update the email customization version. Check the error payload for details. -
1210007:
EMAIL_CUSTOMIZATION_VERSION_DELETE_PROBLEM— We were unable to delete the email customization version. Check the error payload for details. -
1210008:
EMAIL_CUSTOMIZATION_REVISION_NOT_FOUND— We were unable to find the email customization revision. Check that the provided revision ID is correct. -
1210009:
EMAIL_ASSET_UPLOAD_PROBLEM— We were unable to upload the email asset. Check the error payload for details. -
1210010:
EMAIL_ASSET_DELETE_PROBLEM— We were unable to delete the email asset. Check the error payload for details. -
1210011:
EMAIL_ASSET_RETRIEVAL_PROBLEM— We were unable to retrieve email assets. Check the error payload for details. -
1207021:
ACTIVITY_LOG_NOT_FOUND— The activity log was not found. Check the workflow ID provided.
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.
Bug Fixes
-
[Affirm] Onfido and liveness step retries now evaluate the latest check results (instead of incorrectly using the first attempt).
-
[Affirm] Activity log fields for Onfido identity verification now reflect the correct values when a user is approved after a retry.
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