Skip to main content

9.4.0 Release Notes

HYPR 9.4.0 is an Internal Release.

The Internal Release Channel is specifically designed for in-house deployment, targeting both our office and DMO environments. This channel is distinct from those used for customer distribution. It enables our teams to integrate monthly updates, offering prompt access to new features and enhancements. This regular update cycle is key in maintaining an agile and responsive product delivery mechanism.

In contrast, the Enterprise Release Channel, which is employed for customer release, operates on a quarterly update schedule. This less frequent cadence is beneficial for customers who require additional time for adaptation and implementation, ensuring minimal disruption to their business operations. It's important to note that all features released through the Internal Release Channel will be subsequently available in the next scheduled Enterprise Release for our customers.

New Section

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 DateHYPR ProductMinimum RequirementNotes
July 31, 2024HYPR Passwordless for Windows 9.4.0Windows (10, 11)Reboot required if upgrading from 7.6 or below; Security Key Support for Yubikey 5 Plus and Feitian ePass K9 Plus, K40 Plus and their offshoots
July 31, 2024HYPR Passwordless for Mac 9.4.0macOS (High Sierra, Mojave, Catalina, Big Sur, Monterey, Ventura, Sonoma 14.1 [not 14.0])Security Key Support for Yubikey 5 Plus and Feitian ePass K9 Plus, K40 Plus and their respective offshoots
July 31, 2024HYPR Mobile App for Android 9.4.0Android 8.0+
July 31, 2024HYPR Mobile App for iOS 9.4.0iOS 12.4+
July 31, 2024HYPR Server 9.4.0Java Development Kit (JDK) 17+Upgrade to 7.10 required before upgrading to 8.0.0 or higher
July 31, 2024HYPR SDK for Android 9.4.0Android 8.0+
July 31, 2024HYPR SDK for iOS 9.4.0iOS 12.4+
July 31, 2024HYPR SDK for Java 9.4.0Java Development Kit (JDK) 17+
Backward Compatibility

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

Enhancements​

  • [HYPR Passwordless for macOS] Login speed improvements on macOS

  • [HYPR Passwordless for Windows] The enrollment service has been updated to operate in a multi-domain forest

  • [HYPR SDK] The FIDO2 Javascript SDK centralized repository has been created

  • [HYPR SDK for Android] QR scan timestamps have been added to gauge performance

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​

  • The call device/wfa/status has been updated to work with a cluster environment

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

Upcoming Changes​

Entra ID External Authentication Use HYPR as an Entra ID External Authentication Method (EAM), so HYPR can be made available as an external method to users. Contact HYPR if you are interested in early adoption of this feature.

Smart Card PIN Unblocking Key (PUK) PIN Reset HYPR accommodates smart card and security key PUK PIN reset functionality from the desktop.

HYPR Enterprise Passkey - FIDO2 Gateway Fallback HYPR provides a fallback mechanism in the event which an existing WiFi or BLE configuration has challenges. HYPR Mobile App will communicate through Control Center to complete CTAP operations with the HYPR Passwordless client.

Control Center: Standard Mode: Expansions to UI, Branding, and Customization Custom Branding expands to add HYPR Passwordless client UI customization from Control Center, and brings forward the legacy UI Branding for the HYPR Mobile App and Push Notifications.

[Control Center] An Entra ID Provisioning API Microsoft's new API allows HYPR to programmatically create an Azure FIDO2 credential (login.microsoft.com). With this API, HYPR users will no longer need to login into Microsoft's website to pair the Enterprise Passkey separately.

Bug Fixes​

  • [Control Center] Fixed: When deleting an email from HYPR Support Access allowable emails, long emails escape the modal boundary

  • [Control Center - Adapt] Fixed: 'Adapt unavailable' selected option is not saving properly

  • [Control Center - Affirm; Keycloak] Fixed: HYPR Affirm is not added to Keycloak's HYPR authenticator after upgrading to 9.3

  • [Control Center; API] Fixed: Swagger index is getting blocked with a 400 error

  • [Control Center; HYPR Mobile App] Fixed: Deleting user devices from Control Center doesn't delete the RP application from affected devices

  • [HYPR Enterprise Passkey + HYPR Mobile App for Android] Fixed: When deregistering the linked security key for a hybrid account, the workstation pairing is also removed

Known Issues​

  • [Control Center - Adapt] FIDO2 authentication attempts are not blocked when FIDO2 is not exempted and the Authentication Failure Threshold is exceeded

  • [HYPR Mobile 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 Passwordless - Both] QR Fallback - The RP application name is cut off when the tenant name is long

  • [HYPR Passwordless for Windows] Deleting a fingerprint from the middle of the list doesn't re-order the rest of the list

  • [HYPR Passwordless for Windows] HYPR displays an error when a paired Yubikey Bio MPE has the maximum number of fingerprints stored already

Breaking Changes​

Android Configuration (Migration from 8.7.X to 9.1.X)​

  • Project-wide:

    targetSdk 33 -> 34
    minSdkVersion 23 -> 26
    kotlin version  1.7.22-> 1.9.20

  • gradle-wrapper.properties:

    https\://services.gradle.org/distributions/gradle-7.6-bin.zip -> https\://services.gradle.org/distributions/gradle-8.4-bin.zip

  • project:build.gradle:

    kotlin version  1.7.22-> 1.9.20
    com.android.tools.build:gradle:7.2.2 -> com.android.tools.build:gradle:8.1.4
    com.google.gms:google-services:4.3.14 -> com.google.gms:google-services:4.4.0
    com.guardsquare:dexguard-gradle-plugin:1.3.24 -> com.guardsquare:dexguard-gradle-plugin:9.4.21

  • app:build.gradle:

    • Implementation:

        androidx.appcompat:appcompat:1.5.1 -> androidx.appcompat:appcompat:1.6.1
        com.google.android.material:material:1.7.0 -> com.google.android.material:material:1.10.0
        androidx.lifecycle:lifecycle-process:2.5.1 -> androidx.lifecycle:lifecycle-process:2.6.2
        com.google.code.gson:gson:2.10 -> com.google.code.gson:gson:2.10.1
        org.apache.commons:commons-lang3:3.12.0 -> org.apache.commons:commons-lang3:3.13.0
        com.google.mlkit:barcode-scanning:17.0.0 -> com.google.mlkit:barcode-scanning:17.2.0
        androidx.core:core-ktx:1.9.0 -> androidx.core:core-ktx:1.12.0
        androidx.lifecycle:lifecycle-viewmodel-ktx:2.5.1 -> androidx.lifecycle:lifecycle-viewmodel-ktx:2.6.2
        org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.7.22 -> org.jetbrains.kotlin:kotlin-stdlib:1.9.20
        com.google.firebase:firebase-messaging:23.1.0-> com.google.firebase:firebase-messaging:23.3.1

    • annotationProcessor:

      androidx.lifecycle:lifecycle-common-java8:2.5.1 -> androidx.lifecycle:lifecycle-common:2.6.2

  • You might need to add this (depending on your setup) in app:build.gradle:

    android {
      ...
          compileOptions {
              sourceCompatibility = JavaVersion.VERSION_1_8
              targetCompatibility = JavaVersion.VERSION_1_8
          }
          kotlinOptions {
              jvmTarget = "1.8"
          }
      ...
    }