- 📙 Audit Monitor
- 🔎 EpicAuth 4.x for Hyperdrive
- 🔍 EpicAuth 3.x for Hyperspace
- 📗
EPCS Solution
- High-Level Product Description and Features
- 📂 Release Notes
- Product Guide
- 📁 Enrollment Guide
- 🗂️
Installation and Configuration
- Upgrading from prior versions
- System Requirements
- Software Requirements
- HealthCast EPCS Server Installation and Configuration
- HealthCast EPCS SAML certificate conversion and deployment
- HealthCast EPCS Install on Citrix
- HealthCast EPCS Install on Enrollment Workstation
- Server Configuration for EPCS
- Creating Reports for SSO Audit Monitor
- Obtaining Records and Reports
- Solution Architecture
- Troubleshooting
- 📕
ExactAccess ('XA')
- ExactAccess 4.14.1
- ExactAccess 4.14.3
- SnapApp Extension
- XA Server
- Installation and Upgrading
- First Time Installation
- Start Here
- Target System Requirements
- Configure Directory Service
- Manual Configuration
- Example Output
- Domain Controller Round Robin
- Domain Controller Settings
- Administrative Role
- Cache Memory
- ProxCard Server
- Local Record Count
- E-Mail Configuration
- Remote Authentication Server
- Testing your Installation
- Passthrough (ProxAuth)
- Upgrade
- Service Configuration
- First Time Installation
- XA Server Administration
- Server Release Notes
- Installation and Upgrading
- XA Client
- Installation and Upgrading
- Customizations
- Workflows
- Configuration
- Logoffcleanup
- ADPWR
- Logging Optimization
- ExactAccess 4.14.0
- XA Client Administration
- HCI Deploy Publisher
- Prior XA Client Releases
- Release 4.12.3 Client
- Release 4.12.0 Client
- Release 4.11.6 Client
- Release 4.11.x Client
- Release 4.11.0 Client
- Release 4.11.1 Client
- Release 4.11.2 Client
- Release 4.11.3 Client
- Release 4.11.5 Client
- Release 4.11.4 Client
- Release 4.11. Client
- Release 4.14.0 Client
- Release 4.12.4 Client
- Release 4.13.2 Client
- How To
- Troubleshooting
- 📒
LYNX Proxcard Management
- Release Notes
- Installation and Upgrades
- Lynx Product Overview
- Move Badge Data From a QAS SQL Database to a Lynx Database
- Installation Checklist
- Lynx Release 1.7.0
- Solution Architecture
- QwickACCESS Client Compatibility
- Configuration Overview
- Step 1: Edit and run the PowerShell script
- Step 2: Edit the INI file
- Step 3: Configure the SQL Login
- Step 4: Run the SQL script to create the database tables
- Step 5: Configure the Lynx Service ‘Log On As’ Account
- Test the Configuration
- Install/Upgrade/Uninstall
- Administration
- Troubleshooting
- 💳
QwickAccess ('QA')
- QA Product Guide
- QA Introduction
- QwickAccess for IGEL
- QwickACCESS to Windows
- QwickACCESS Server
- QwickAccess for Dell ThinOS
- QwickACCESS for HP ThinPro OS
- QwickACCESS to VDI for Windows
- Licensing
- QA Troubleshooting
- QA & Lynx How-To
- QA Product Guide
- 💡
FAQ
- Badge FAQs
- Badges Not Registered When Pointing to XA 4.11.x Server
- Ignore New Badge - Currently Processing an Existing Badge Tap
- Badge Reader is Not Processing Badges After Upgrading to Windows+10 v1809
- Badge Tap Fails After Installing or Upgrading XA Client
- No Response from Badge Tap on Thin Client Connected to VDI
- XA is Not Recognizing RDR-7012AKU When it's Plugged In
- XA Client FAQs
- XAdrivemapping.exe Produces An Access Violation Error (intermittent)
- Apps Launched From XA Fail to Start as Expected
- Invalid XA User Caused by Forward Slash in AD Object Name
- HP Laptops - Display Going Black on XA Login Screen (Conextant Flow.exe)
- User Receives Desktop Error - Parameter Width is Insufficient - After Upgrading to XA Server 4.11.x
- Logoffcleanup PowerShell Script Opening in Notepad
- xaDriveMapping.exe Causes High CPU Usage
- Known Issues
- Frequently Asked Questions (FAQ)
- FAQs and Troubleshooting
- FAQ for AD-PWR
- XA Server FAQ
- How to determine the number of unique users based on badge (prox) usage
- 4.x How to configure Logoff Cleanup
- Virus Scanning Exclusions
- How to assign XA Toolbar Favorites using Roles
- Remove all badge records older the X days
- How to Customize the user display name on the XA Toolbar and Privacy Shield
- FAQ #1 How to configure policies...
- FAQ #2: How to configure the RunAs Connector
- FAQ #3: How to enable logging for xaLogoffCleanup
- XA Server/SQL FAQ
- Administration FAQs
- Known Server Issues
- Troubleshooting Topics
- Logging Overrides
- Anti-virus Directory and Port Exclusion Recommendations
- Stored Badge Password Cleared in Under 120 Minutes
- Audit Data From Client Systems is Not Being Written to Audit Database
- Users Unable to Authenticate Using Remote Authentication
- XA Server Event Log Error - XADATALAYER.CLSUSERS.GetUserRoles Error - Access Denied
- Remote Authentication
- XA Server Logging
- XA Server Stops Responding to Client Requests
- XA Server Troubleshooting Checklist
- Windows Profiles on XA Server
- Anti-virus Directory and Port Exclusion Recommendations
- hciserverconfigure Error After Adding Domain to NT DS Configuration
- Manual Configuration
- XA ProxCard Administrator
- Epic Hyperdrive FAQs
- Badge FAQs
- 💡 Best Practices All Products
- Support Bulletins
- 📖 Glossary
Institutional Enrollment
- Updated on 01 Dec 2022
- 3 Minutes to read
- Contributors
Institutional enrollment can only be conducted by DEA-registered institutional practitioners and must be completed in-person.
This process will require that the user be added to the RapidIdentity MFA server. Once the user is enrolled, they can then proceed to enroll for the PingMe service. Proceed to Adding Users to the RapidIdentity MFA Server to continue with this type of enrollment.
Institutional Enrollment Overview
Reference the below steps to complete the Institutional Enrollment process.
- The user must be added to the RapidIdentity MFA server.
- Log out of the Admin Portal and have the user complete the user steps
- Enroll the User for PingMe Service.
- Enroll the User with Fingerprint Biometrics.
Adding Users to the RapidIdentity MFA Server
Follow the proceeding steps to enter the provider(s) into the MFA Server.
- Under the Administration Portal, select the Users tab.
- Select New Users from the left-side menu.
- Enter the following desired user information:
- Username
- Domain
- Language
- Phone Number
- Select the appropriate Authentication Set and Role.
- Select Add.
User Steps
To complete setup, log out of the Admin Portal and have the user perform the following steps.
- Have the user enter the Username and domain.
- The user will be taken to the RapidIdentity User Portal.
- Press Continue to set up new credential(s).
- The user will be prompted to set up and confirm a password.
- Note: This password will be linked to the fingerprints that will be captured in the following step.
- Note: This password will be linked to the fingerprints that will be captured in the following step.
- The user will then select the finger they wish to enroll.
- Note: The person assisting in the enrollment process can guide the user through this process to ensure they select the fingers that are desired by the organization for authentication.
- Note: The person assisting in the enrollment process can guide the user through this process to ensure they select the fingers that are desired by the organization for authentication.
- Have the user place the matching finger onto the sensor to begin initializing the fingerprint registration.
- Important: Different scans are required in order to validate the fingerprint. The user will need to lift and place a finger on the sensor to obtain various scans.
- Important: Different scans are required in order to validate the fingerprint. The user will need to lift and place a finger on the sensor to obtain various scans.
- Repeat the steps above until the number of required fingerprints for registration is obtained.
- Note:
- Up to all ten fingerprints can be validated.
- Once fingerprints are validated, click Next.
- The user will then be prompted to click on which type of OTP will be enrolled. Instruct the user to select the second option that involves enrolling a mobile device or soft token application.
- Note: Hard token is another option available to select.
- Note: Hard token is another option available to select.
- Enter your phone number and carrier and select Send SMS.
- The user will receive an on-screen notification that the process is complete. At this point, they will select Continue to proceed to the User’s Portal home page.
- The user will be prompted to finish enrollment on the mobile device
Once the user receives the SMS on their cell phone, they will enter the information provided on the SMS into the RapidIdentity mobile app and proceed to follow the on-screen prompts to complete their enrollment.
User Steps
To complete setup, log out of the Admin Portal and have the user perform the following steps.
- Have the user enter the Username and domain
- User will be taken to the RapidIdentity User Portal.
- Press Continue to setup new credential(s).
- The user will be prompted to set up and confirm a password
- NOTE: This password will be linked to the fingerprints that will be captured in the following step.
- User will then select the finger he/she wishes to enroll
- NOTE: The person assisting in the enrollment process can guide the user through this process to ensure they select the fingers that are desired by the organization for authentication.
- Have the user place the matching finger onto the sensor to begin initializing the fingerprint registration
- IMPORTANT: Different scans are required in order to validate the fingerprint. User will need to lift and place finger on sensor to obtain various scans.
- Repeat the steps above until the number of required fingerprints for registration are obtained
- NOTE: Up to all ten fingerprints can be validated.
- Once fingerprints are validated, click Next.
- The user will then be prompted to click on which type of OTP will be enrolled. Instruct user to select the second option that involves enrolling a mobile device or soft token application
- NOTE: Hard token is another option available to select.
- NOTE: Hard token is another option available to select.
- Enter phone number and carrier and select Send SMS.
- The user will receive an on-screen notification that the process in complete. At this point, he/she will select Continue to proceed to the User’s Portal home page.
- The user will be prompted to finish enrollment on the mobile device
- IMPORTANT: Once the user receives the SMS on their cell phone, they will enter the information provided on the SMS into the RapidIdentity mobile app and proceed to follow the on-screen prompts to complete their enrollment.