Skip to main content

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
PGA of America Partnership
Secure What's Next
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

FAQ: How does the Authenticator keep connected

Expand / Collapse


This article applies to:

  • R3000/WF/WFR 3.0.x - to 4.1

 

Question:

  • How does the authenticat stay connected?

Reply:

Once authenticator client starts working it continually sends a "heartbeat" to the filter - with a specified interval of seconds between each heartbeat until the end user logs off. 

Notes:

Please note if your having issues with authenticat.exe, please upgrade to the newest version on the filter and the authenticator deployment kit located on the support website under Downloads and documentation. At this writing the newest version is AuthDeploy-2.0.10.477.msi

 


To contact LevelBlue about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.