11.3.4 Release Notes
HYPR 11.3.4 is a patch to the 11.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.
The per-item record for this release and every prior release is maintained in the Changelog.
Minimum Supported Versions
| Release Date | HYPR Product | Minimum Requirement | Notes |
|---|---|---|---|
| September 4 | HYPR Passwordless for Windows 11.3.4 | 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 its offshoots |
| September 4 | HYPR Passwordless for Mac 11.3.4 | 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 |
| July 24 | HYPR Mobile App for Android 11.3.1 | Android 9.0+ | |
| August 19 | HYPR Mobile App for iOS 11.3.2 | iOS 12.4+ | |
| September 4 | HYPR Server 11.3.4 | Java Development Kit (JDK) 17 | Upgrade to 7.10 required before upgrading to 8.0.0 or higher |
| August 1 | HYPR SDK for Android 11.3.2 | Android 9.0+ | |
| August 19 | HYPR SDK for iOS 11.3.2 | iOS 12.4+ | |
| September 4 | HYPR SDK for Java 11.3.4 | Java Development Kit (JDK) 17+ |
All HYPR components are fully compatible across the three previous/subsequent minor (X.X) HYPR releases.
HYPR Control Center
New Features
▸ HYPRspeed in Safari on macOS
HYPRspeed (Desktop SSO) now works in Safari on macOS. The handoff between the browser and the workstation runs over HTTPS on a HYPR-provided hostname that resolves to the user's own machine, which is what Safari requires of a request made from a secure page. Chrome, Edge, and Firefox are unaffected and continue to work as before. Safari support requires a HYPR Cloud tenant; self-hosted deployments continue to use the earlier handoff.
Contact your HYPR representative to enable Safari support on your tenant. Before you do, review the network controls under HTTP Proxy Support: Desktop SSO. A proxy, DNS filter, or DNS rebinding protection that intercepts the hostname prevents the handoff from reaching the workstation. See also Using HYPRspeed.
▸ Handoff Timeout for Desktop SSO
A new Handoff Timeout (Seconds) setting on the Desktop SSO settings panel controls how long the browser waits for the workstation to answer before falling back to the next login method. Leave it blank to use the default of 60 seconds; the accepted range is 1 to 300.
It is distinct from SSO Timeout (Minutes), which sets how long a completed Desktop SSO session stays valid. See Handoff Timeout.
Enhancements
▸ Direct Handoff to the Local HYPR Agent
Desktop SSO attempts the direct handoff to the local HYPR agent before falling back to the browser-launch method, restoring the order used before release 11.3.2 on workstations that do not yet hold the certificate.
Endpoint requirements for Desktop SSO in an embedded browser are unchanged; see (Windows) Desktop SSO in Embedded Browsers.
▸ Desktop SSO During a Staged Client Upgrade
Desktop SSO now continues to work on workstations that have not yet been upgraded to the client release that introduced origin reporting, so a fleet can be upgraded in stages rather than all at once. See Client Origin URL.
▸ Read-Only Administrators and Desktop SSO Timeouts
The Desktop SSO timeout fields are now read-only for administrators whose role does not permit editing them.
Events
The following events were added in this release:
DESKTOP_SSO_TLS_BUNDLE(WORKSTATION_STATE) — a workstation was issued the certificate that secures the Desktop SSO connection to it. A refusal is logged assuccess=falsewith the reason appended to the message.DESKTOP_SSO_TLS_CERT_EXPIRY_CHECK(SYSTEM_CHECK) — the certificate that secures the Desktop SSO connection to the workstation is approaching expiry.
To see all HYPR events, see Audit Trail Event Descriptions.
Error Messages
The following error codes were added in this release:
- 1201103:
DESKTOP_SSO_TLS_CERTIFICATE_EXPIRING— The certificate securing the Desktop SSO connection to the workstation is close to expiry. Desktop SSO stops working for all users once it expires. Contact HYPR support to have the certificate renewed. - 1201104:
DESKTOP_SSO_TLS_AUTH_AGREEMENT_FAILED— The workstation could not prove its identity when requesting the certificate Desktop SSO needs, so no certificate was issued. Re-register the HYPR client on the affected workstation; if many workstations are affected at once, contact HYPR support.
To see all HYPR errors by component, see HYPR Error Codes Troubleshooting Table.
APIs
You can find detailed descriptors and other API calls in HYPR's full Postman API set here.
The Changelog holds the per-item record of bug fixes and known issues for this release and every prior release.