3rd party SSL install on Windows server 2012 to enable LDAPS

3rd party SSL install on Windows server 2012 to enable LDAPS

Hello experts,

So I need to install an godaddy  SSL cert on my Windows server to enable LDAPS. I was about to purchase the cert when the godaddy rep told me that SSL certs can't be installed on .local domain (mycompany.local) anymore, apparently it was possible years ago.

He told me the work around is to bind teh fqdn to the DC by creating a .local sub domain in a public domain... From what I understood I need to create a .local subdomain in my companies public domain (local.publicdomain.com). I get that part, what I'm confused with is the binding of the DC to the subdomain. Does it mean creating a dns zone for the subdomain and creating a record?

The other solution would've been to have my internal domain with something other than .local but it's a production environment and can't change that.

So can anyone please shed some light on the binding part? Also, I am correct on my assumption of creating a .local sub-domain in my public domain?

Thanks in advanced.
jorge diazSEAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
In such situations, my *strong* recommendation is to not use a public cert. An enterprise CA is almost always a better choice. There is no reason an untrusted device should be connecting to a DC, even using LDAPS, and trusted devices can have the root cert deployed/installed to negate the need toe a public cert.

As with any advice, there are edge case exceptions. But they really are rare when it comes to allowing LDAP connections to a domain controller.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David Johnson, CD, MVPOwnerCommented:
you can create local.example.com but not example.com.local
you can get certs for local.example.com but not example.com.local
jorge diazSEAuthor Commented:
thank you both for you input, however I'm still confuse about the fqdn binding to a DC...
Peter CalderNetwork AdministratorCommented:
The certificate is used for the SSL connection to the DC, not for doing the LDAP query.
As per Cliff Galiher, you will need to build your own PKI and use the certificates from that.
You should create your own root CA, then a subordinate CA, and then issue a certificate with the CN being server.mycompany.local
Push out the root CA certificate to all PCs and servers using group policy.

When an SSL connection is made, the client will check that the DNS matches the CN in the certificate. The client will also need to see the root of the certificate chain in the trusted root CAs in the Windows certificate store.
If DNS matches and the root CA certificate is trusted, the SSL handshake will continue and you will get a secure connection.
jorge diazSEAuthor Commented:
Thank you all for your help. As Cliff and Peter suggested I ended up deploying an internal CA, trying reconfigure the network to get a 3rd party cert for a .local domain was going to be an unnecessary nightmare.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.