asked on

Configuring LDAPS on windows server 2012.

Hi,

I am able to connect and authenticate LDAP over SSL from ldp.exe,
But when i try to connect to it from browser( ldaps://localhost:636 ), i am unable to connect.

can anyone please help me with this.
i have applied self-signed SSl certificates.

Is there something we should do to access it from browser, because while trying to connect from ldp.exe i am not facing any issue.

Please help me with this.

Thanks in advance.

George Simos

To my knowledge it is not supposed to be accessible from a web browser. It's a service accesible on a specific port for a specific protocol. What are you trying to achieve by accessing ldaps from a browser?

ganesh marella

ASKER

Hello George,

Thanks for sharing your knowledge.

Actually i work in a product based company and our product deals with mails and all.

So we got a request from customer asking about this. so we started exploring about this.

And we are able to connect from browser to normal ldap by:
ldap://localhost:389

but we are not able to connect to ldaps from browser by:
ldaps://localhost:636

Is there any possible way so that we can work on that.

Thank you.

ASKER CERTIFIED SOLUTION

George Simos

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ganesh marella

ASKER

Hi George,

That was really helpful.

Just for an update while using ldp.exe what i observed is that it is ldap_sslinit function for connecting to LDAPS while it is using ldap_open for LDAP.

Thank you so much for the help.

George Simos

Hi ganesh,

Thanks for accepting my answer, actually this was one of my first observations about the ldap:// connection uri by using the LDP tool, after that I researched a bit and found that there are differences in the various implementations regarding the URI construction, it was also stated that LDAPS was non-standard and that made me go the other way around.
You may find more info in this wikipedia article "Lightweight Directory Access Protocol" and navigate to the "URI Scheme" section.
Also it is interesting that the SSL implementation is stated as dropped in 2003! ;-)