Job execution fails when configured for a Radius overlay.
The Director box hangs after executing this job towards one SG. To recover, a reboot is necessary.
Using WP5-GBL Authentication in our Radius overlay file, causes the job to fail, and the Director appliance to hang.
If a special character ! <Exclamation mark> is used at the beginning of encryption key - then the overlay file will error out.
There were two issues discovered with this issue.
1: The Radius command line interface command was wrong.
Using the Command "show config" in the command line interface ( CLI) command, we see this configuration output for Radius:
; Configure Authentication Realms
! - BEGIN RADIUS for Admin Authentication
; Configure authenication realm for admin access
security radius create-realm Radius_Admin_Auth @(RADIUS_ADMIN_AUTH_SERVER_1) 1812
security radius edit-realm Radius_Admin_Auth
primary-server secret @(RADIUS_ADMIN_AUTH_SECRET_1)
alternate-server secret @(RADIUS_ADMIN_AUTH_SECRET_2)
alternate-server @(RADIUS_ADMIN_AUTH_SERVER_2) 1812
! - END RADIUS for Admin Authentication
In the above command, the SECRET key is missing.
In this Overlay -provided above - the RADIUS is configured with the command
" security radius create-realm Radius_Admin_Auth @(RADIUS_ADMIN_AUTH_SERVER_1) 1812"
2: The secret key cannot contain a exclamation mark "!" for these reasons:
NOTE1: For an overview of how to setup Radius on a Director appliance, see FAQ337
NOTE2: For a list of what Radius vendors Bluecoat supports, see FAQ1125
Rate this Page
Please take a moment to complete this form to help us better serve you.