HYPR Documentation Portal

HYPR is the leading provider of True Passwordless Security with millions of users deployed across the Global 2000.

Shared secrets are the #1 cause of enterprise breaches, fraud and phishing attacks.

HYPR is the first Authentication Platform designed to eliminate passwords and shared secrets - effectively removing the hackersโ€™ primary target while eliminating fraud, phishing and credential reuse for consumers and employees across the enterprise.

Customer Authentication 6.3.0

What's New?

Release Date




Server 6.3.0



Android SDK 6.3.0
iOS SDK 6.3.0

Android & iOS

Summary of Changes

HYPR's August 2020 release introduces new features to the Workforce Access product, including magic links for user registration directly from within the mobile app, improved tools for support desk troubleshooting, and enhancements to the Control Center user experience.

In addition, this release brings several focused improvements to the SDK including the resolution of bugs in the iOS simulator, the ability for Android SDK developers to set a regex for pin complexity, and more.

New Features

Control Center UI Enhancements
The Control Center branding has been changed to make the fonts and styling consistent across all screens and navigation. Additional UI improvements include removing redundant navigation options and changing deprecated or modified information (removed tertiary color choice for app, updated workstation login toggle to classify for domain joined users). The Control Center also now shows the current version number. For more information, see the Control Center 6.3 page.

Logging & Troubleshooting
To improve the HYPR end user experience and aid support desk troubleshooting, HYPR has normalized the logs which are ingested and used across the SIEM infrastructure, added a Trace ID to group together separate user transactions such as registration and authentication, and provided a mechanism to retrieve historical error messages from the HYPR Mobile App. For more information, please see the new Retrieving & Debugging Mobile Device Errors page.

Magic Links for Registration Directly in Mobile App (Beta)
Control Center admins can now generate magic links which allow end users to perform mobile registration directly from their mobile devices without a web interface. An audit trail logs each time an admin generates a magic link and records details of the generated request such as username and other system management information. The initial release of this feature focuses on a use case that employs Slack to communicate magic links to the end users. For more information, please see the new Registration with Magic Links page.

Bug Fixes & Improvements:

  • Resolved crash when unpairing web account on Android
  • Added Trace ID to the Audit Trail. For more information, please see the Audit Trail page.
  • Updated Android QR Scan library
  • Android SDK developers can set a regex for pin complexity (see here for documentation)
  • Resolved xcode warnings with _Nonnul & _Nullable annotations on iOS

Known issues


The event table did not get updated with the traceId table.

ERROR 2020-08-12 00:42:38,894 main [,][] SpringApplication.reportFailure(837) : Application run failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eventEntityManager' defined in class path resource [com/hypr/server/commons/cloud/event/EventDBConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean]: Factory method 'eventEntityManagerFactory' threw exception; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: EventService] Unable to build Hibernate SessionFactory;

Add the missing column manually.

alter table fido.events add traceId varchar(255) null;
alter table fido.events_bkp add traceId varchar(255) null;

Updated 9 months ago

Customer Authentication 6.3.0

What's New?

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.