LDAP-AD Not Working - Hyland - 4174

Hyland Community

I am trying to configure LDAP-AD for Alfresco. I added the authenticator "example.com" with the following values:

Format: Default

LDAP server URL: ldap://server.example.com:389

Security: simple

Security Principal Name: svc_alf@example.com

Security: simple

Security Principal Credentials: XXXXX

LDAP Synchronization: Enabled

I configured the User Search Base and Group Search Base using dn consistent with my environment.

I then ran synchronization. Here are the results:

Example.com

LDAP (Active Directory)

True

True

1 Group Analysis	Start Time: 25 Jan 2017 14:19:44 End Time: 25 Jan 2017 14:19:44	Successful: 0 Failed: 0	Percent Complete: 100% Total Results: 0
6 User Creation and Association	Start Time: 25 Jan 2017 14:21:51 End Time: 25 Jan 2017 14:22:54	Successful: 2 Failed: 0	Percent Complete: Unknown Total Results: 1

When I try to test, I get the following error:

Authentication Test Result

Test Failed

Authentication Message

00250957 Failed to authenticate, authenticator with name, example.com, not found

Test Diagnostics

Authenticator not found:

Failed

Any help would be greatly appreciated!

6 REPLIES 6

Sounds like you used the Admin Console to set this up. That means you are using Alfresco Enterprise Edition, and any support requests should typically go to Alfresco directly via the support portal (support.alfresco.com).

Did you really setup your LDAP server with the DNS name ldap.example.com? Otherwise this cannot work... On the other hand, you seem to have two users sucessfully synchronised.

I did use the Admin Console, thank you for the support tip.

No, I did not actually use example.com, lol.

Hi:

For confirmation: Did you use "user" as login or "user@example.com" in the ldap test ? You need to put "user" (sAMAccountName) in the login. You may check with "svc_alf" for example.

Regards.

--C.

I did use a valid sAMAccountName for the test.

What is weird, is that since I posted this, I tested logging into the admin console using an AD account and it was successful. So it would appear that the authentication mech is working, but the "test" feature is not.