Secure Mobile Access 12.4 Administration Guide

User Access Agents

User access agents are deployed to client devices based on the community to which the user belongs. Most agents are deployed automatically when the user logs in to the WorkPlace portal using a browser. The installation package for these two access agents can also be made available for download from a file share on your network or deployed through applications such as Microsoft’s Systems Management Server (SMS) or IBM’s Tivoli. For more information, see Selecting Tunnel Access Methods for a Community.

When deployed automatically—when a user logs in using a browser—the access agents are both deployed and activated on the first visit. This generally requires the user to accept a download for the Secure Endpoint Manager (SEM), which will in turn manage the access agent installation and future access agent updates. On subsequent visits to the WorkPlace portal from the same client device using the same browser, the access agents are automatically activated without user intervention. See Client and Agent Provisioning (Windows) for more information.

The below table compares the capabilities of access agents and lists their requirements. For other system requirements, see Client Components.

Access agent comparison
Network tunnel access (IP protocol)Proxy access (TCP protocol)Web access (HTTP protocol)
OnDemand Tunnel agentConnect Tunnel clientOnDemand Mapped ModeTranslated, Custom Port mapped, Custom FQDN mapped Web access
Application support
TCP-based client/server applicationsxxx
TCP- or UDP-based client/server applicationsxx
URLs and Web applicationsxxxx
Windows networking
Web-based file accessxx
Native Windows file access (Network Neighborhood)xx
Mapped network drivesxx
Windows domain logonx
Connection types
Forward connectionsxxxx
Reverse connections (such as FTP or SMS)xx
Cross-connections (such as VoIP)xx
Operating systems
Linux or Macintoshxxxx
Administrator privileges required to install client/agentxx
Auto-activated from WorkPlacexxx
Provisioned from WorkPlacexx1
Provisioned outside of WorkPlacex
  1. Port-mapped mode requires ActiveX or Java. For a user without administrator rights who can’t run ActiveX, the Java Runtime Environment (JRE) is used.

Was This Article Helpful?

Help us to improve our support portal

Techdocs Article Helpful form

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.