Go to the table of contents Go to the previous page Go to the next page View or print as PDF
RADIUS authentication
Help | Content Gateway | v8.5.x
Content Gateway supports the RADIUS option to ensure that users are authenticated with a RADIUS server before accessing content through the proxy.
When the RADIUS option is enabled:
*
*
*
*
Content Gateway supports a primary RADIUS server and a secondary RADIUS server for failover. If the primary server does not respond to the proxy request within the specified timeout (60 seconds by default), Content Gateway tries to check the username and password again. If a response from the primary RADIUS server is not received after the maximum number of retries (10 by default), the proxy contacts the secondary RADIUS server. If Content Gateway cannot contact the secondary RADIUS server, the user is prompted again for a username and password.
The RADIUS cache is held in memory and stored on disk. Content Gateway updates the data on disk every 60 seconds. In addition, Content Gateway stores username and password entries in the RADIUS cache for 60 minutes. If a password and username entry is expired in the RADIUS cache, Content Gateway contacts the RADIUS server to accept or reject the username and password.
To configure Content Gateway to be a RADIUS client:
*
*
See Configuring Content Gateway to be a RADIUS client.
Configuring Content Gateway to be a RADIUS client
1.
Go to Configure > My Proxy > Basic > General.
2.
3.
Navigate to Configure > Security > Access Control > Radius.
4.
5.
6.
7.
8.
Click Apply.
9.
Click Restart on Configure > My Proxy > Basic > General.
 
Note 
Setting RADIUS cache and server timeout options
By default, the RADIUS cache and RADIUS server timeout options are configured as follows:
*
*
Change these default values by editing the records.config file.
1.
Open the records.config file located in /opt/WCG/config.
2.
 
3.
4.
From the Content Gateway bin directory (/opt/WCG/bin), run content_line -L to restart Content Gateway on the local node or content_line -M to restart WCG on all the nodes in a cluster.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Copyright 2020 Forcepoint. All rights reserved.