Authentication with LDAP server failed because received empty DN for user

[Carracido]

Hello community,

I have an issue and maybe you know the reason. Here the situation:

Trying to create an authentication profile to authenticate with active directory but it´s not working.

When testing the profile with "test authentication ... " command I get the following error:

Authentication to LDAP server at X.Y.Z.E for user "......"
Egress: X.X.X.X
Type of authentication: GSSAPI
Starting LDAPS connection...
Succeeded to create a session with LDAP server
Received empty DN for user "my_user"
Authentication failed against LDAP server at X.X.X.X:636 for user "my_user"

Do you have any idea why it´s receiving empty DN?

For example, LDAP works as the groups can be customised in the 'allow-list'

Thank you in advance,

Carracido.

[S.Cantwell]

Ok, best to ask some questions first.

Is this a new implementation/install/configuration with LDAP authentication?

Has your LDAP server profile (along with domain name, distinguished name (service account), etc., work, for authenticating a test administrator account, vs testing for authentication policies?

DN to me could ne DOMAIN Name or Distiguished Name.  When you wrote back "empty DN", do you think it mean Domain or Distinguished (just curious... not really a troubleshooting step)

Does your authentication profile include the Login Attribute filled out to be samAccountName? (again, just a confirmation, not so much for troubleshooting)

Test with an admin, whose authentication requires LDAP, before testing your authentication policy.

Let me know the answers, and we can proceed from there.