Skip to main content

9.3.1 Release Notes

HYPR 9.3.1 is a patch to the 9.3.0 Enterprise Channel Release.

The Enterprise Release Channel caters to customers requiring a less frequent cadence of upgrades, specifically on a quarterly basis, thereby allowing them more time to adapt and implement changes without disrupting their business operations.

The Standard Release Channel is designed for customers who are equipped to accommodate monthly updates, providing regular and more frequent access to new features and improvements. All Standard Release features are available in the next scheduled Enterprise Release.

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
Aug 1, 2024HYPR Passwordless for Windows 9.3.1Windows (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
Aug 1, 2024HYPR Passwordless for Mac 9.3.1macOS (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
Aug 1, 2024HYPR Mobile App for Android 9.3.1Android 8.0+
Aug 1, 2024HYPR Mobile App for iOS 9.3.1iOS 12.4+
Aug 1, 2024HYPR Server 9.3.1Java Development Kit (JDK) 17+Upgrade to 7.10 required before upgrading to 8.0.0 or higher
Aug 1, 2024HYPR SDK for Android 9.3.1Android 8.0+
Aug 1, 2024HYPR SDK for iOS 9.3.1iOS 12.4+
Aug 1, 2024HYPR SDK for Java 9.3.1Java Development Kit (JDK) 17+
Backward Compatibility

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

New Features​

  • [Control Center - Integrations] HYPR Enterprise Passkey - Entra ID FIDO2 Provisioning APIs [Alpha] 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.

  • [HYPR Passwordless for Windows] Security Key PIN PUK support APIs, Events, and error codes have been added to the documentation in anticipation of full Security Key PIN PUK Management functionality.

Enhancements​

  • [All HYPR] General UI Improvements

  • [Control Center] Custom Branding now includes the ability to delete your custom icon

  • [HYPR Passwordless for Windows] A progress spinner has been added during the pairing process

  • [HYPR Mobile App for Android] Single Registration: An option has been included to add multiple workstations even if one is already present

Events​

The following Events and parameters were added in 9.3.1:

  • SECURITY_KEY_PUK_READ

  • SECURITY_KEY_PUK_UPDATE

  • SECURITY_KEY_PUK_DELETE

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

Error Messages​

The following Errors have been added to HYPR:

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

APIs​

  • [HYPR Passwordless] Security Key PIN PUK Management operations have been added:

    • POST /cc/api/securitykey/getpinreset: Obtain the security key PUK value..

    • POST /cc/api/securitykey/updatepinreset: Update the security key PUK value.

    • POST /cc/api/securitykey/deletepinreset: Delete the security key PUK value.

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 providea 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 [Beta] 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.

[Control Center] Quicksight Analytics Dashboards HYPR adds the power of Amazon QuickSight graphs to our Analytics Dashboard, including several useful views; this will replace the legacy dashboard in an effort to consolidate the look and feel across HYPR reports.

Bug Fixes​

  • [Control Center] Sanitized Firebase credentials from Control Center logs

  • [Control Center - Integrations] Removed client secrets from server's response

  • [Control Center - Platform] Fixed: Keycloak events are not getting generated, and do not appear in the Audit Trail

  • [HYPR Mobile App for iOS] Fixed: Single Registration: Web to Workstation - Device Manager displays two computer bubbles after pairing, when it should display only one

Known Issues​

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

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

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

  • [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 maximuum number of fingerprints stored already

  • [HYPR Passwordless for Windows] If the YubiKey minidriver is already installed, a reboot might be required for the new version to take effect due to pre-loaded DLLs; until the reboot, all YubiKey authentications can potentially fail

  • [HYPR Affirm; Keycloak] HYPR Affirm is not added to Keycloak's HYPR authenticator after upgrading to 9.3

Breaking Changes​

  • Google Firebase Cloud Messaging Discontinued

    Google Firebase terminated the usage of legacy Firebase Cloud Messaging (FCM) APIs, effective June 20, 2024. This will affect most HYPR customers; if you have not taken measures to accommodate this change, please contact HYPR Support ASAP.

  • 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"
            }
        ...
      }