— Exhibit –Info AUT23457 2012-07-16 18:20:06 – ive – [192.168.252.1] jsmith(Users)[] – Login failed using
auth server Corp (LDAP Server). Reason: Failed
Info AUT24327 2012-07-16 18:20:06 – ive – [192.168.252.1] jsmith(Users)[] – Primary
authentication failed for jsmith/Corp from 192.168.252.1
Minor AUT23391 2012-07-16 18:20:06 – ive – [192.168.252.1] jsmith(Users)[] – Could not connect
to LDAP server ‘Corp’: Failed binding to admin DN: [49] Invalid credentials:
ADCorp.acme.com:389
Info AUT23457 2012-07-16 18:20:01 – ive – [192.168.252.1] rbook(Users)[] – Login failed using
auth server Corp (LDAP Server). Reason: Failed
Info AUT24327 2012-07-16 18:20:01 – ive – [192.168.252.1] rbook(Users)[] – Primary
authentication failed for jsmith/Corp from 192.168.252.1
Minor AUT23391 2012-07-16 18:20:01 – ive – [192.168.252.1] rbook(Users)[] – Could not connect
to LDAP server ‘Corp’: Failed binding to admin DN: [49] Invalid credentials:
ADCorp.acme.com:389
— Exhibit —
Users are reporting that they cannot log in to the Junos Pulse Secure Access Service. In the user
access log on the Junos Pulse Secure Access Service, you discover a series of messages shown
in the exhibit.
What is the cause of the problem?
A.
The Junos Pulse Secure Access Service cannot reach the LDAP authentication server.
B.
The Junos Pulse Secure Access Service cannot authenticate to the LDAP authentication
server.
C.
The users are failing authentication because their LDAP credentials are invalid.
D.
The users are failing authentication because they do not exist in the LDAP directory.
Explanation: