No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


After configuring Agile Controller as LDAP server for eSight, the selected users don't have administrator rights

Publication Date:  2018-05-29 Views:  376 Downloads:  0

Issue Description

Fault symptom: Agile can be configured as Radius server for eSight users, but when the customer configured this scenario, the users didn't have administrator privilege even if the authorization rule was configured correctly. 

Version information: Agile Controller-Campus V100R003C50 

Operation scenario: Agile Controller is Radius server for eSight and the users configured in Agile can authenticate in eSight.

Guide: From eSight documentation: The Agile Controller Serves as the RADIUS Server to Authenticate eSight Login Users


I asked the customer to check if the user matched the authorization that was created on Agile Controller-Campus. Regarding the configuration on both sides, since the users could authenticate but they didn't have privilege I suspected that they didn't match the authorization rule created in Agile Controller.

For example, I created test_radius on Agile and I use it to login on eSight and I have administrator rights:

In Agile this user is matching the authorization that I created and it has administrator rights :

This is the authorization matched result: 

Authorization rule :

To be sure that it is matching the right authorization rule I advised the customer to adjust this rule with the highest priority and use as authorization conditions the user/group that it was created for eSight.