Overview
Enterprise Endpoint Detection and Response (EDR), antivirus, and endpoint protection solutions may block Windows Login v2.0 components during installation or authentication. To ensure successful deployment and uninterrupted passwordless authentication, configure the required allowlisting (whitelisting) policies in your endpoint security solution.
The recommendations in this document apply to commonly used endpoint security products such as Microsoft Defender for Endpoint, CrowdStrike Falcon, SentinelOne, VMware Carbon Black, Trellix (McAfee), Sophos Intercept X, Trend Micro Apex One, Cortex XDR, and Cisco Secure Endpoint.
Supported Endpoint Management Solutions
Endpoint Security Solution | Allowlisting Required | Recommendation |
Microsoft Defender for Endpoint | Yes | Configure Process, Folder and ASR Exclusions |
CrowdStrike Falcon | Yes | Create Prevention Exclusions for Oloid processes and installation folder |
SentinelOne | Yes | Create Application, Process, and Folder Exclusions |
VMware Carbon Black | Yes | Approve Oloid application through Application Control policy |
Trellix (McAfee) | Yes | Configure On-Access Scan and Access Protection exclusions |
Sophos Intercept X | Yes | Configure Local Exclusions for files, folders, and processes |
Trend Micro Apex One | Yes | Add Oloid applications to Trusted Program List |
Cortex XDR | Yes | Create Process and Path Allow Rules |
Cisco Secure Endpoint | Yes | Configure Custom Allow List policies |
Note: These antivirus solutions may stop the services during installation.
Recommended Allowlisting
Category | Item | Recommendation |
Installation Folder | Oloid installation directory | Allow the complete installation folder from scanning and behavioral analysis. |
Executables | Windows Login application binaries | Allow all Oloid executable files. |
Windows Services | Oloid Windows services | Allow service execution and startup. |
Credential Provider | Oloid Credential Provider | Do not block or quarantine the Windows Credential Provider. |
DLL Files | Oloid DLLs | Allow all DLLs installed with Windows Login v2. |
Registry | Oloid registry entries | Allow read/write access required by the application. |
Local Communication | Named Pipes / IPC / Localhost | Do not block communication between Oloid components. |
Network | HTTPS (TCP 443) | Allow outbound communication to required Oloid endpoints. Refer to the Windows Login v2 Network URL Whitelisting guide. (oloid.help) |
Windows Login v2 Components to Allowlist
Component | Executable / File | Purpose | Required |
Windows Login Application | Oloid Passwordless Login.exe | Windows passwordless authentication application | Yes |
Supervisor Application | OloidPasswordlessAdminNew.exe | Endpoint administration and configuration | Optional |
Oloid Launcher | OloidLauncher.exe | Launches configured applications after authentication | Optional |
Apache CouchDB | CouchDB Service | Local database installed with Windows Login v2 | If Local Cache is enabled (oloid.help) |
Installation Folder
Item | Recommendation |
Default Installation Folder | Allow the complete Oloid installation directory. |
Custom Installation Folder | If a custom path is used during installation, allowlist the custom installation directory instead. |
Registry Keys
Registry Location | Recommendation |
HKLM\Software\Oloid | Allow read and write access. |
Windows Credential Provider registry | Do not block Credential Provider registration. |
Network Requirements
Protocol | Port | Action |
HTTPS | TCP 443 | Allow outbound communication to all required Oloid endpoints. |
Refer to:
Troubleshooting
Issue | Recommendation |
Application fails to launch | Verify executable allowlisting. |
Windows Credential Provider is missing | Verify the Credential Provider DLL is not blocked by endpoint security. |
Authentication fails | Review EDR logs for blocked processes or services. |
Installation is blocked | Verify the installation folder and executable exclusions. |
Services do not start | Verify service execution is permitted by the endpoint security policy. |