RadSec - TLS Encrypted RADIUS Protocol

The latest RADIUS version supports the TLS interface and can be used in the SmartZone controller to support a TLS connection with the AAA server as a RadSec proxy.

The RadSec proxy establishes the TLS connection with the RadSec AAA server using TLS over TCP. In the web interface, if TLS is enabled in the authentication or accounting service, RAC sends RADIUS messages to the RadSec proxy, and the RadSec proxy forwards the RADIUS messages over TLS to the configured RadSec server.

The connection between controller and RadSec server lasts for a maximum of 30 seconds. As soon the controller receives a new Authentication Requests, it initiates a TLS handshake towards RadSec. If network is down or RadSec server (process) is down, then (user equipment) UE authentication FAIL.

Note: If the connection between controller and RadSec is broken, by default the connection is resumed when the next message is received from the client. If the connection is not re-established, the administrator should verify if the network is down or RadSec server is down as noted above.

TLS cipher suites are not user-configurable. The following cipher suites are supported by controller (RadSec client):

  • ECDHE-RSA-AES128-GCM-SHA256
  • ECDHE-RSA-AES256-GCM-SHA384
  • ECDHE-ECDSA-AES128-GCM-SHA256
  • ECDHE-ECDSA-AES256-GCM-SHA384

In FIPS mode, client authentication and accounting messages are exchanged through a TLS tunnel established between vSZ and the AAA server. This ensures that the user name, password, passphrase, or any other sensitive information pertaining to the user or user session is encrypted.