Troubleshooting: AnyConnect Embedded Browser Does Not Create a Device Fingerprint

Version Affected: All
 
 

Overview

The Cisco AnyConnect embedded browser does not create a device fingerprint for the user.

Cause

This occurs when the Public/Private Mode option on the realm's Workflow tab is changed from Public mode only (or Public and Private modes) to Private mode only, while the AnyConnect embedded browser still holds a SecureAuthLoginsecureauthXX=PUBLIC cookie from before the change. Device fingerprinting only works when that cookie is in PRIVATE mode, so the embedded browser cannot create a fingerprint until the cookie is refreshed under the new setting.

Resolution

Rename the following folder to force the embedded browser to clear its cookies, then sign in through AnyConnect again to set a new SecureAuthLoginsecureauthXX=PRIVATE cookie:

C:\Users\[username]\AppData\Local\Cisco\Cisco AnyConnect Secure Mobility Client\EBWebView

Special Considerations

Renaming the EBWebView folder also clears the embedded browser's cached passwords, permissions, and cookies — not just the one causing this issue.
 
 
 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.