RADIUS Setup
Follow these steps to start the RADIUS server, configure its parameters, and set the RADIUS secret.
Starting the RADIUS server service
The -u <uuid> parameter is required. From the install directory (cd <INSTALL>):
./startGoAuthProxy.bsh -u 7e9e71aa-3ad3-11ee-be56-0242ac120002 -rTo start on port 1815 (default is 1812), use the -p <port> option:
./startGoAuthProxy.bsh -p 1815 -u 7e9e71aa-3ad3-11ee-be56-0242ac120002 -rTo start with a proxy password:
./startGoAuthProxy.bsh -p <proxy password> -u 7e9e71aa-3ad3-11ee-be56-0242ac120002 -rTo start with a new RADIUS secret:
./startGoAuthProxy.bsh -s <new secret> -u 7e9e71aa-3ad3-11ee-be56-0242ac120002 -rRADIUS server configuration parameters
-r <true|false>— required to start the RADIUS server. Can be used together with the LDAP-lparameter to start both servers. Default isfalse;truestarts the RADIUS server along with the LDAP server.-P <port>— override the default RADIUS port (1812).-s <new secret>— override the default RADIUS secret value,secret.The default RADIUS secret
secretshould only be used for testing. For production servers, always use a secure secret string.If the secret contains bash shell special characters, escape it to prevent bash from interpreting the characters as shell commands.
Configuring the RADIUS secret
Your RADIUS client and RADIUS goauthproxy server must be configured with the same shared password (secret). The maximum length is 256 bytes and it is case sensitive. A shared secret of at least 16 characters is recommended.
Port 1813 using the default secret
./startGoAuthProxy.bsh -p 1813 -u 20783f4d-fc7a-4133-b379-1224f1e3c92e -r
Port 1812 using the default secret
./startGoAuthProxy.bsh -u 20783f4d-fc7a-4133-b379-1224f1e3c92e -
Port 1813 using the escaped secret
./startGoAuthProxy.bsh -p 1813 -u 7e9e71aa-3ad3-11ee-be56-0242ac120002 -s secret\$pecialchar\(12\) -r
Stopping the RADIUS server service
Run stopGoAuthProxy.bsh:
1814 (RADIUS)
./stopGoAuthProxy.bsh -P 1814
RADIUS event logs in AdminX
The RADIUS server generates Event Logs whenever a user successfully or unsuccessfully authenticates using RADIUS.
E_LOGIN_SUCCEEDED — created when a user completes RADIUS authentication using Push or OTP. Details captured: Tenant Info, referrer_name = RADIUS, Time of Event, Username, User IP Address, RADIUS client identifier, RADIUS client name, Login method (push, otp).
E_LOGIN_FAILED — created when a user fails RADIUS authentication. Details captured: the same fields listed above.
Last updated
Was this helpful?

