/
Anonymous vs. Authenticated Server Authentication
Anonymous vs. Authenticated Server Authentication
Should you have a provisioned Bind User DN (Distinguished Name) and Bind Password needed for the LDAP service, perhaps for a power user, or in cases where anonymous access is not granted by policy, you can use those values to provide another level of security between NetMRI and the servers comprising the LDAP service.
An anonymous bind takes place as follows:
2015-05-01 17:41:59 Anonymous bind
2015-05-01 17:41:59 Authentication successful.
An authenticated bind, using the correct Bind User DN and Bind Password appears as follows:
2015-05-01 18:23:06 Authenticate 'cn=root,dc=infoblox,dc=com'
2015-05-01 18:23:06 Authentication successful.
Related content
Anonymous vs. Authenticated Server Authentication
Anonymous vs. Authenticated Server Authentication
More like this
LDAP Authentication Service Configuration
LDAP Authentication Service Configuration
More like this
LDAP Authentication Service Configuration
LDAP Authentication Service Configuration
More like this
Using a Certificate File for an LDAP or AD Service
Using a Certificate File for an LDAP or AD Service
More like this