Describes Configure Identity Providers for Experience Insights in Cisco Secure Access. Identity provider configuration integrates your organization's identity sources with Secure Access to enable user-centric monitoring in Experience Insights.
Identity provider configuration integrates your organization's identity sources with Secure Access to enable user-centric monitoring in Experience Insights. This configuration allows the system to map OS-authenticated user identities to ThousandEyes-managed endpoints, providing a comprehensive view of network performance by user rather than by device.
Prerequisites
-
Agent Version: The ThousandEyes Endpoint Agent must be version 2.13.3 or later.
-
Identity Integration: Your organization must have an Active Directory (AD) or Identity Provider (IdP) integration configured with Secure Access via SCIM or AD Connector.
-
Supported identity providers:
-
Windows: Active Directory (AD) and Entra ID.
-
Mac: Mosyle, JAMF Connect, Enterprise Connect, Kerberos, and Managed Preference.
-
-
User Domain: The user must be part of the customer organization domain.
-
Authentication: The device running the ThousandEyes endpoint agent must have the user logged in and authenticated.
-
Single user sessions: Devices with multiple users logged in and authenticated at the same time are not supported.
Benefits of Identity Mapping
When you configure your identity provider, Experience Insights uses a translation layer to associate ThousandEyes endpoint data with identity information. This mapping provides several benefits:
-
Correlation of issues by user group: Isolate connectivity issues to a specific user group to streamline troubleshooting and ensure targeted remediation.
-
Intuitive Troubleshooting: Search for endpoints using first and last names of a user to identify the correct device across your organization. This approach is more intuitive than using a device name and helps reduce the mean time to resolution for connectivity issues.
Identity Resolution Logic
The name and email displayed in the dashboard are not necessarily based on the currently logged-in user. Instead, the system uses an identifier associated with the device to look up the user in your identity directory.
If a device has more than one possible identifier, the system uses them in the following order:
-
Zero Trust Access (ZTA) client identity: Used first, if available.
-
Cisco Secure Client (RAVPN) identity: Used next.
-
Other device records: Includes records with an identity, such as URC or Umbrella.
-
Logged-in username: Used only as a final fallback.
Identity Mapping Considerations
Consider the following behaviors when reviewing identity information:
-
Offline device status: If an endpoint meets all identity resolution criteria but is currently offline, Secure Access displays the last seen user identity associated with the device.
-
Synthetic test impact: When a synthetic test is executed, the displayed user identity might update based on the configured test interval and the data collected during that specific test run.
Fallback Behavior
If a device does not meet the identity resolution criteria, Experience Insights defaults to displaying the ThousandEyes username instead of the user's full name.