Edit RADIUS Server Files

You may need to modify one or more RSA RADIUS server files. For example, you may need to edit these files if you are configuring a RADIUS client that has special attribute names that need to be included in the RADIUS profiles or if you are changing the default RADIUS authentication ports 1645, UDP, and 1812, UDP, and the firewall rules for those ports.

Edits apply only to the RADIUS server on which you make the changes.

Note:  Be cautious when editing the configuration files. The changes that you make are not validated, and the existing file is overwritten with the new content. For a detailed explanation of the syntax used in the configuration files, see the RSA Authentication Manager RADIUS Reference Guide.

Before you begin 

You must have Super Admin and Operations Console administrator credentials.

Procedure 

1. Log on to the Operations Console on the RSA Authentication Manager primary instance.

2. Click Deployment Configuration > RADIUS Servers.

3. If prompted, enter the Super Admin User ID and password, and click OK.

4. Select the RADIUS server that you want to update, and select Manage Server Files from the context menu.

5. On the Manage Server Files page, do one of the following:

   • Click the Configuration Files tab to see the configuration files, such as .conf and .ini.

   • Click the Dictionary Files tab to see the RADIUS dictionary files.

6. Select the file that you want to edit, and select Edit from the context menu.

7. Edit the text file, and click Save.

8. Click Save & Restart RADIUS Server for the changes to take effect.

After you finish 

You must copy to other RADIUS servers any edits that must be synchronized across the environment, such as edits to dictionary.* files. To copy edits to another RADIUS server in the deployment, select the appropriate RADIUS server from the manage RADIUS Servers page on the primary instance, and copy or make the edits.

Replica attachment automatically updates the RADIUS server on the replica instance with any dictionary file edits that were made to the RADIUS server on the primary instance. For example, any custom dictionaries added on the primary instance are available on the replica instance, and modifications made to the master dictionary or vendor.ini file on the primary instance are automatically updated on the replica instance. After replica attachment completes, you must manually copy to other RADIUS servers any RADIUS dictionaries or dictionary file edits that must be synchronized across the environment.