Introduction
OLOID provides a robust tap-to-login and tap-badge-to-logout solution designed to enhance security and productivity across Windows native apps. This document outlines the standard process we follow for all customers, detailing the steps to integrate these features into your environment as part of a Proof of Concept (POC).
The POC typically includes identifying target applications—whether they are Windows native apps, web apps, or virtualized apps. OLOID will develop and deploy customized autofill automation for each app across your machines. This document covers the generic steps involved in setting up the process.
System Requirements
Operating System: Windows 10 and above (Windows Server is not supported)
Network: Internet access is required for package updates and connecting to OLOID APIs.
Prerequisites
Hardware: Badge readers compatible with OLOID’s tap-to-login and logout solutions.
.Net Library and Python Installed on the machines.
Access to the target applications for integration and automation.
Standard Process for Setting Up Proof of Concept (POC)
Step 1: Download and Unzip the Setup Package
OLOID provides a ZIP file containing the necessary configuration and automation scripts.
Download and locate the ZIP file on your system.
Right-click the file and select Extract All to unzip the package contents.
Choose a destination to extract the files.
Step 2: Navigate to the Internal Folder
Once the files are extracted, navigate to the folder.
Open the EVN folder, which contains the configuration files necessary for setup.
Step 3: Configure Application Settings
Open the Config Folder: Inside the EVN folder, navigate to the config directory.
Edit Configuration: Open the configuration file and ensure the settings for the application are appropriate (e.g., for Zoom or Skype).
Step 4: Retrieve the Application Path
Locate the Application: Open the Windows search bar, type the name of the application, and locate it (e.g., “Zoom” or “Skype”).
Find the File Path: Right-click the application and select Open File Location.
Copy the Shortcut Location: Right-click the app shortcut and select Open File Location again.
Update the Config File: Copy the address from the address bar, append the application executable (e.g., \zoom.exe or \skype.exe), and save the changes in the config file.
Step 5: Start the Automation Process
Open TapLoginInitiator: Return to the extracted folder and open TapLoginInitiator
Start Automation: Launch the relevant automation process by selecting the corresponding application logger (e.g., Zoom Logger or Skype Logger).
POC Objectives and Standard Customer Engagement Process
Identifying Target Applications
As part of our standard POC process, OLOID collaborates with customers to identify the target applications—whether they are Windows native apps, web apps, or virtualized apps. Based on this identification, we develop specific autofill automation for each application, ensuring seamless login/logout functionality across your environment.
Customer Collaboration
For a successful POC, OLOID requires the following from our customers:
Access to Windows 10 or higher machines or virtual machines (VMs) where the POC will be conducted.
Permissions to the relevant target applications (e.g., Zoom, Skype) for testing and automation purposes.
Coordination with OLOID to replicate the POC scenario across 2-3 systems, enabling thorough user acceptance testing (UAT).
Once these components are in place, OLOID will:
Test and validate the automation processes.
Collaborate with your team to fine-tune configurations.
Prepare the environment for full deployment following successful UAT completion.
User Experience
Tap-to-Login Flow:
User Badge Tap: Users will tap their badge on a compatible badge reader.
Secure Retrieval of Credentials: Once the user is identified through the badge tap, OLOID’s secure vault retrieves the user’s credentials (username and password).
Autofill and Login: The system autofills the retrieved credentials into the pre-configured application (e.g., Zoom or Skype) and logs the user in automatically.
Session Start: The application opens, and the user is ready to start their session without manually entering login credentials.
Tap-Badge-to-Logout Flow:
User Badge Tap: To end the session, the user taps their badge on the reader again.
Automatic Logout: The system logs the user out of the application, securely ending the session.
Session Termination: The application is closed, and the system is ready for the next user to log in with their badge.
This seamless experience allows users to access applications quickly and securely without manual input, making it ideal for environments where shared devices and rapid session changes are common.
Conclusion
OLOID's integration process for tap-to-login and tap-badge-to-logout is designed to ensure ease of use, security, and scalability. Our standardized POC approach guarantees consistent and reliable results across different environments. Should you have any questions during setup, please contact your OLOID account manager or reach out to our technical support team for assistance.