The customer configures RADIUS remote authentication and login on eSight. The RADIUS server interconnects with the AD server and synchronizes some accounts from the AD server to the RADIUS server. When a user uses a local account of the RADIUS server, the user can successfully log in to eSight, but fails to log in to eSight when the user uses an account from the AD server.
The AD server supports only PAP authentication packets but does not support CHAP. To solve this problem, change CHAP on eSight to PAP because the final account information is verified on the AD server.