How to change the RADIUS authentication port on Authentication Manager 8.1
Originally Published: 2015-10-11
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1
Issue
This article provides information on how to change the default RADIUS authentication ports of 1645 and 1812 to a non-standard ports.
Resolution
1. Login to the Operations Console and select Deployment Configuration > RADIUS Servers.
2. Click on the context arrow next to the name of the RADIUS primary server and choose Manage Server Files.
3. Click on the context arrow next to the radius.ini file and select Edit.
4. Scroll to the [Ports] section. Note that UDPAuthPort is used for RADIUS authentication and UDPAcctPort is for RADIUS accounting.
5. Change the port number according to the business requirements. By default the entries will look like the example below:
[Ports] TcpControlPort = 1812 ;TcpControlAddress = 1.2.3.4 SecureTcpAdminPort = 1813 ;SecureTcpAdminAddress = 1.2.3.4 UDPAuthPort = 1645 UDPAcctPort = 1646 UDPAuthPort = 1812 UDPAcctPort = 1813 ;UDPProxyPortBlockStart = 28000 ;UDPProxyPortBlockLength = 64
[Ports] TcpControlPort = 1812 ;TcpControlAddress = 1.2.3.4 SecureTcpAdminPort = 1813 ;SecureTcpAdminAddress = 1.2.3.4 UDPAuthPort = 2500 UDPAcctPort = 1646 UDPAuthPort = 1812 UDPAcctPort = 1813 ;UDPProxyPortBlockStart = 28000 ;UDPProxyPortBlockLength = 647. Click Save and Restart RADIUS Server for the change to take effect.
8. If there are any replicas in the deployment, the radius.ini for the replica can be changed through the primary server’s Operations Console. To do this, repeat Steps 4 – 9 for each replica.
An alternative way to make the change would be to login as the rsaadmin user to the primary server via SSH, vSphere or a direct connection.
1. Navigate to /opt/rsa/am/radius.
2. Open the radius.ini file in a text editor.
3. Edit the [Ports] section as in the samples above.
4. Navigate to /opt/rsa/am/server and restart the RADIUS service using the command ./rsaserv restart radius.
5. Repeat steps 1 – 4 on each replica in the deployment.
Related Articles
How to change the failed authentication thresholds in RSA SecurID Number of Views How to change the explicit Change Request (CR) name to include the CR details in name section in RSA Identity Governance a… Number of Views How to close ports used by the RSA Authentication Agent to block SSLv3 communication to RSA Authentication Manager 8.x Number of Views Weak Certificate Signature Hashing Algorithm on TCP ports 5550 & 5580, CVE-2004-2761, CVE-2005-4900 Number of Views RSA Announces the Availability of RSA Identity Management and Governance 6.9.1 Patch 131 Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA SecurID Authentication Engine 3.0.0 for Java Release Notes RSA Authentication Manager 8.3 Dell 630 and 230 hardware appliance loses ability to access keyboard when running PING 4.0 … RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?
