RADIUS service address filtering

For extra security, you can limit access to RADIUS services by entering an IP address for a specific network adapter or by adding a list of IP addresses (such as for VPN servers). This ensures that unauthorized hosts can't access RADIUS services.

The agent can restrict traffic based on one or both of the following parameters. A request must satisfy both parameters if they're set.

Parameter What it does If not set
ragent.network.accept.allow_list (version 2.30.0 and later) The agent drops packets from any host that isn't on the list. It doesn't accept the connection or process the packets. The agent accepts connections from any host.
ragent.client_ip_allow_list (version 2.28.0 and later) The agent filters packets after it processes the requests. You can set it for all RADIUS apps on the agent or per port. On a new installation, the agent doesn't listen on any port.

To configure address filtering:

  1. Go to the config.properties file in the installation folder of the RADIUS app. If the app is installed with the default settings, the file path is the following:
    C:\Program Files (x86)\Okta\Okta RADIUS Agent\current\user\config\radius\
  2. Back up the configuration file to ensure that you can recover from editing mistakes.
  3. Open the config.properties file with any text editor.
  4. Optional. To limit access to a network adapter, add the following entry to the file. Replace <IP address> with the IP address that you want to use:
    ragent.network.bind = <IP address>
    For example, to accept a connection where 10.10.10.110 is the adapter IP address, enter the following:
    ragent.network.bind = 10.10.10.110 
  5. Optional. If your RADIUS agent version is 2.30.0 or later: To drop traffic from unlisted hosts before the agent processes it, add the following entry to the file. Replace each <IP address> with the IP address of a VPN server that sends RADIUS requests to the agent:
    ragent.network.accept.allow_list = <IP address>, <IP address>
    For example, to accept packets only from 10.20.30.40 and 10.20.30.41, enter the following:
    ragent.network.accept.allow_list = 10.20.30.40,10.20.30.41
  6. If your RADIUS agent version is 2.28.0 or later: To limit client access for all RADIUS apps configured on this agent, add the following entry to the file. Replace each <IP address> with the IP address that you want to allow:
    ragent.client_ip_allow_list = <IP address>, <IP address>, <IP address>
    The following values are allowed:
    • The * symbol (allow any client).
    • A comma-separated list of IP addresses.
    • A value of none, deny, or no value assigned (the agent doesn't listen on that port).
  7. If your RADIUS agent version is 2.14.0 to 2.28.0, it's recommended to upgrade. To do so, add the following entry to the file to limit client access. Replace each <IP address> with the IP address that you want to use:
    ragent.network.accept.allow_list = <IP address>, <IP address>, <IP address>
    For example, to accept packets from a client using 10.10.10.15, 10.10.10.16, or 10.10.10.17, enter the following:
    ragent.network.accept.allow_list = 10.10.10.15, 10.10.10.16, 10.10.10.17
  8. Recommended. For orgs with multiple RADIUS apps on this agent, to allow different clients per app, add the following entry to the file. Replace each <IP address> with the IP address that you want to allow:
    ragent.client_ip_allow_list.<port> = <IP address>, <IP address>
    For example, to allow different clients on two apps, enter the following:
    ragent.client_ip_allow_list.1812 = 10.0.0.5,10.0.0.6
    ragent.client_ip_allow_list.1645 = 10.0.1.10
  9. Save the file and restart the okta-radius service for your changes to take effect.
  10. To confirm which ports the agent is listening on, check the agent log file:
    • An INFO entry indicates that a port is restricted to specific IP addresses.
    • A WARN entry indicates that a port allows any client (*).
    • A message saying Not listening on port(s)... indicates a port with no valid allowlist.
  11. Not recommended. If you want to preserve the behavior of your RADIUS agent from versions earlier than 2.28.0, add the following entry to the file:
    fileragent.client_ip_allow_list = *

Production configuration example

Though the parameters ragent.network.accept.allow_list and ragent.client_ip_allow_list are independent, a typical production environment uses both. For example:
# Network accept allowlist: only these hosts can reach the agent
ragent.network.accept.allow_list = 10.20.30.40,10.20.30.41
# Client IP allowlist: which clients can use each RADIUS port
ragent.client_ip_allow_list.1812 = 10.20.30.40
ragent.client_ip_allow_list.1645 = 10.20.30.41

In the previous example, a request from 10.20.30.40 to port 1812 satisfies both parameters. The agent drops requests from any other hosts based on the ragent.network.accept.allow_list parameter.