The user experience with the Nymi Solution starts with a one time Nymi Band enrollment in the Nymi Band Application.
The enrollment process takes less than 5 minutes to complete and associates user credentials to a Nymi Band.
Administrators manage the enrollment experience and how the user can use their Nymi Band by configuring individual or group policy settings on the Nymi Enterprise Server(NES).
Before the start of each shift the user wears their Nymi Band and then performs fingerprint or corporate credentials authentication to activate the Nymi Band. After successful authentication, the user can use the Nymi Band to perform contactless hand free logins, e-signatures and physical access on different endpoint devices and applications.
There are currently 2 main use cases for the Nymi Solution:
- Passwordless login and e-signature, which is where the user unlocks their desktop and completes the signatures by tapping their Nymi Band near the Bluetooth adapter or NFC reader that is attached to the user terminal.
- Physical access, which is where the user unlocks a door by tapping their Nymi Band on or near the door access panel.
To use the Nymi Band to complete authentication tasks, you require an a Nymi-Enabled Application(NEA) that integrates with the Nymi solution. There are three types of integration.
| Direct Integration | Application that includes the Nymi SDK
and interacts directly with the Nymi Solution to
support the completion of authentication tasks with a Nymi Band. For example, POMSnet. This type of integration usually requires some configuration changes in the application to define key components in the customer environment, such as host names. For more information about how to use the Nymi Band with direct integration applications, refer to the Nymi Integration Guides section on the Nymi Support site. Nymi provides you with two direct integration applications, as described later in this document.
|
| Middleware(SSO Integration) | Application requires an additional piece of software to
enable communication with the Nymi components. For example, Evidian Enterprise
Access Management (EAM). An SSO integration usually requires you to perform some
configuration changes to define key components in the environment, and in the case
of Evidian, you manually copy the nymi_api.dll file to the
Evidian installation directory.
For more information about using the Nymi Band with EAM to complete authentication tasks in applications such as PAS-X, refer to the Nymi with Evidian Solution—Deployment Guide for more information. |
| Open Standards | Applications relies on open standards to communication with the Nymi components. For example, the Nymi Band can store FIDO2 credentials, which a
FIDO2-enabled application can access while the Nymi Band remains authenticated. The Nymi Band is a certified FIDO2 authenticator and
certified as Microsoft-compatible. This type of integration usually requires some
changes to the open standards biometric authentication configuration.
For more information about how to use the Nymi Band with FIDO-2 enabled applications, review the Nymi Connected Worker Platform—FIDO2 Deployment Guide. |
Comments
0 commentsPlease sign in to leave a comment.