@Vincent-TP 

First of all, thank you for providing the procedure. I have already configured the LDAP in our controller.

At first, I updated the firmware version of the controller and then configured the LDAP Profile. The list of the OUs and CNs is appearing, I chose Domain Users, so I am expecting that when the domain user logs in, the AD will authenticate the user. Unfortunately, that is not the case. When I tried to login, the error appears. Please see screenshots of configuration and errors.

Am I missing something here?

  @Vincent-TP 

Please see the result of the ping.

  @OliverN 

Hi, can you try to use sAMAccountName for identifier

I tried this and it works on my side. Hope this works on you too

  @Jeesoon1 

Hi @Jeesoon1 

I tried the configuration you've suggested, but now I received a different error.

Even though my credential is correct, still it doesn't work. I tried to log in on my PC and on the AD server itself, and I can log in without a problem.

What am I missing here? Do I need the certificate from the AD server?

Hi All,

I finally made it work!!!


It looks like the Active Directory server is talking on a different port, 3268, which is LDAP GC. I also changed the format of the Regular DN.

Thank you very much to all of those who help me.

Hope this will also help other people.

Thank you everyone.

  @OliverN 

Have you tried it using VPN with LDAP authentication ?

And did it work ?

  @Jeesoon1 

I already made it work. You can see on my previous reply.

Thank you.