What is the difference between RSA ACE/Agent 5.x for UNIX and a Communications Server?
Originally Published: 2002-08-27
Last Modified: 2023-09-25
Article Number
Applies To
RSA ACE/Server
Communications Server
Issue
Types of RSA ACE/Agent Hosts
Technical and functional differences among Agent Hosts
Resolution
There are five types of Agents in the ACE/Server architecture (listed below). Although similar in functionality, there are specific technical and functional differences among them. Hence, an agent of one type might not work properly when its corresponding agent record specifies the wrong type of agent.
1. Communication Server: Remote access server or network access server (NAS), router, or firewall produced by a company that integrates RSA ACE/Agent code into its devices.
The authentication procedure might take longer on a communications server agent. As a result, the Server will have to calculate a wider authentication window --compared to a UNIX or Net OS agent.
If ACE/Server RADIUS is being used, there must be two agents: a) one of type Net OS Agent for the RADIUS server and b) one of type Communication Server for the NAS. The Agent Record of the Communication Server will contain the RADIUS encryption key shared between the ACE/Server RADIUS and the NAS.
2. Single-Transaction Comm Server: A communication server, router, or firewall produced by a company that integrates RSA ACE/Agent code into its devices. It can perform only the standard Enter PASSCODE and PASSCODE Accepted or Access Denied dialog.
3. Net OS Agent: Uses RSA ACE/Agent for Windows NT, Windows 2000, iPlanet Web Server, Domino Web Server, Novell NMAS, Novell NetWare Connect, or OpenVMS.
4. UNIX Agent: Uses RSA ACE/Agent for UNIX. After authentication, the sdshell included with this agent will use the default shell value to launch the corresponding UNIX shell for the user.
5. NetSP Agent: This agent is a Single-Transaction Comm Server, thus, it will send the node secret. However, it will not support the Next Token Code or New Pin modes. This is considered a legacy agent type and it is rarely used now.
Related Articles
Real time system log monitor shows error handling OA request: No shared ciphers for protocol after upgrading to RSA Authen… Number of Views Workflow shows 'Workflow flagged as stalled based on stall detection settings' error in versions 6.9.1 and 7.0 of RSA Ide… Number of Views Alias host name redirect to consoles is not working after upgrade to RSA Authentication Manager 8.3 patch 1 Number of Views Microsoft Windows update MS16-101 breaks RDP from the RSA Authentication Agent 7.3.1 for Windows for all RSA challenged users Number of Views VERIFY_ERROR and authentication failure using REST method with RSA Authentication Agent for PAM with RSA Authentication M… Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent for UNIX Platform Support Matrix
Don't see what you're looking for?
