The IDex Client is an application, which acts as a miniature local proxy on macOS workstations and Windows NT Workstations. It forwards usernames, group membership, and information about web requests to the Smoothwall Filter for web filtering purposes. Each web request is identified individually, and it can identify multiple users logged in at the same workstation. Local user accounts are identified by the workstation, and users behind a NAT connection.
The IDex Client runs without any interaction from your end-users, gathering necessary information directly from the workstation. This has the advantage of not being reliant on a working connection to your domain controllers to be able to function correctly — so long as users can log into the workstation, information can be captured. Additionally, no direct communication path is needed between the Smoothwall Filter and Firewall and the Active Directory.
With Microsoft DirectAccess systems, HTTPS could potentially be used to establish a tunnel back to the organization network. In such instances, the external IP or host, configured in the DirectAccess server configuration must be excluded from the proxy configuration to prevent failure. This failure is caused by the outgoing connection for the IP-over-HTTPS tunnel attempting to connect through the IDex Client to reach the Smoothwall Filter and Firewall proxy via the same tunnel.
Note: When an off-site client system connection is established through DirectAccess, the DirectAccess server IP address are seen in the User Activity page instead of the client device’s IP address.
For installation and interface setup, see the help topics:
Something not right? Send us feedback.