Skip to main content

9.6.0 Release Notes

HYPR 9.6.0 is an Internal 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
Sept 26, 2024HYPR Passwordless for Windows 9.6.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
Sept 26, 2024HYPR Passwordless for Mac 9.6.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
Sept 26, 2024HYPR Mobile App for Android 9.6.0Android 8.0+
Sept 26, 2024HYPR Mobile App for iOS 9.6.0iOS 12.4+
Sept 26, 2024HYPR Server 9.6.0Java Development Kit (JDK) 17+Upgrade to 7.10 required before upgrading to 8.0.0 or higher
Sept 26, 2024HYPR SDK for Android 9.6.0Android 8.0+
Sept 26, 2024HYPR SDK for iOS 9.6.0iOS 12.4+
Sept 26, 2024HYPR SDK for Java 9.6.0Java 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] New Device Registration End-User Notification End users receive an alert email when a new device is added to their account.

[HYPR Adapt] Signal Search Tab We've introduced a new tab designed to quicly access all the signals that have come within a certain timeframe. Each row will have the Event name, Event time, and Event source, and additional details may be expanded.

[Control Center] Entra ID FIDO2 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 their Enterprise Passkey separately.

[HYPR Passwordless for Windows] Password Prompt Removal for Windows [Proof of Concept] HYPR provides administrators with the possibility during Passwordless installation to remove the Windows password prompt for a passwordless experience for their users.

Enhancements

  • [Control Center - Integrations] Entra ID External Authentication Methods (EAM) username is now pre-populated using data from Entra

  • [Control Center] Custom Branding - Logo & Background section contains toggles to enable/disable branding by product (Adapt/Affirm/Authenticate/Keycloak)

  • [HYPR Adapt] Allow users to change the time period for Signal Handler metrics; previously the only option was 24 hours

  • [HYPR Adapt] An additional HMAC key has been included for use with the test event

  • [HYPR Adapt] An InTune-specific policy is used to schedule verification of whether or not macOS machines are managed

  • [HYPR Adapt] Custom policy secret values instructions (i) have been added

  • [HYPR Adapt] Policy Assignment table UI/UX updates

  • [HYPR Adapt] Risk Reports - policyID column name has been changed to policyName

  • [HYPR Adapt] Signal Handler Metrics Overview has been added above the main handlers list enumeration; it includes (from the last 24 hours) the total signals received (as number), total signals ingested successfully vs. unsuccessfully (as a donut chart), and the most-ingested events (as a bar chart)

  • [HYPR Adapt] Signal Handler template icons reflect the associated vendor

  • [HYPR Adapt] Signal Handler templates have been added for Event Enricher handlers

  • [HYPR Adapt] Signal handler test tab is available for custom handler code in similar fashion to Adapt Custom Policy testing

  • [HYPR Adapt] When the administrator selects the Block Authentication option for the Evaluation Response Unavailable Fallback dropdown, a warning message displays about the repercussions of the selection; i.e., all users will be blocked from authentication until Adapt is back online

  • [HYPR Affirm] A custom outcome is now available for instances where a requester is denied

  • [HYPR Affirm] Identity Verification Flow now can include connections between requester and approver based on user directory, SMS, email, and OIDC

  • [HYPR Passwordless for macOS] Added extra logging to detect TouchID usage from the OS before displaying the Unlock dialog

  • [HYPR Passwordless for Windows] IE SmartCard Hook now includes the fields type, model, and form (e.g., USB-A or USB-C) of security keys in the HYPR preSmartKeyEnroll server hook

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

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

Upcoming Changes

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

HYPR Documentation Reorganization In the 10.x series, HYPR Documentation will undergo minor but still notable changes in the way articles are grouped. Instead of adhering to the legacy format mirroring the UI layouts, based on feedback from customers, we are making accommodations in an attempt to better reflect the user's journey.

Bug Fixes

  • [Control Center] Fixed: Device Manager users can issue unauthorized DELETE calls to remove devices that are not theirs

  • [Control Center] Fixed: Transaction flow fails to render activity screen

  • [Control Center] Fixed: User table misalignment

  • [HYPR Adapt] Fixed: Risk Reports Events are not sorted by the eventtimeinutc column

  • [HYPR Affirm] Fixed: The escalation approver should not be able to choose an automated approver as an option.

  • [HYPR Mobile App for Android] Fixed: Enterprise Passkeys - Android stops issuing the /deviceapi/fido2/receive calls when trying to register a security key again after deregistering a previous Entra pairing

  • [HYPR Passwordless for macOS] Fixed: Failure to contact Certificate Authority if user is accessing a shared folder

  • [HYPR Passwordless for macOS] Fixed: QR Fallback - The application cuts off the tenant name if it is too long

  • [HYPR Passwordless for Windows] Fixed: Incorrect elements being read on the error screens, and WFA crashes on selecting one of them

  • [HYPR Passwordless for Windows] Fixed: On domain-joined machines, the hover properties are missing for Smartphone /Security key icons on the Select your device to continue screen

  • [Platform - Keycloak] Fixed: Select your login page carat (^) covers text on the screen while hovering over 'Hypr Mobile App'

Known Issues

  • [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 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

  • [Control Center] Server still sends push notifications with incorrect proxy credentials

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