RADIUS authentication functions correctly for the Management Center Web Graphical User Interface (GUI), but fails for Secure Shell (SSH) or Command Line Interface (CLI) sessions. This behavior occurs when the RADIUS server authenticates the user but does not provide the required authorization attributes to grant CLI access.
SSH/CLI login attempts return "Access Denied" or "Authentication Failed" when users log into the Web GUI successfully via RADIUS.
Symantec Management Center 3.x
External RADIUS Server (FreeRADIUS, Cisco ISE, Microsoft NPS, etc.)
CLI logins require authorization by the Vendor-Specific Attributes (VSAs). If the RADIUS server does not return the Blue-Coat-Group attribute, or if the user’s group is not assigned a role with "CLI Access" permissions in Management Center, the session is terminated.
Configure RADIUS Server & Group Synchronization Settings
Configure the Access Role:
Map the RADIUS Group
1. RADIUS server's dictionary file must contain the following entries:
VENDOR BlueCoat 14501
BEGIN-VENDOR BlueCoat
ATTRIBUTE Blue-Coat-Group 1 string
END-VENDOR BlueCoat
2. RADIUS server's client configuration file must contain the following items:
MC's IP address
Shared Secret (case-sensitive shared key)
3.RADIUS server's user file must contain the user's password and the group information:
e.g. testuser1 Cleartext-Password := "XXXXXX" Blue-Coat-Group = "MCCliAdmins" (based on an example above)
Ref: Configure Cisco ACS for Management Center