Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an ASP MVC app that's supposed to be hosted on our DMZ server. What's the best practice to secure the network when connecting to the LDAP server?

share|improve this question

migrated from May 23 '12 at 20:32

This question came from our site for professional and enthusiast programmers.

This is a networking question and not relevant to a programming site, regardless of whether you are dealing with MVC or not. – Erik Funkenbusch May 23 '12 at 16:49

I'm making a few assumptions here because your question doesn't really specify. Those are:

  • The DMZ server is standalone and not joined to the company's Active Directory (if one even exists)
  • The LDAP server you refer to is not the company's Active Directory

If those are both correct, your only option really is to connect to the LDAP server over SSL. This will obviously require setting up the LDAP server to be accessible over SSL if it's not already. The downside is that you ultimately have to embed the LDAP authentication credentials somewhere in your app.

On the other hand, if the DMZ server is a member of the company's Active Directory and the LDAP server you're connecting to is that same Active Directory domain, you should be running the Application Pool as a domain service account (with whatever AD permissions it needs for its task). Then, connecting to LDAP can be done via Kerberos and you wouldn't have to embed any credentials within the site to connect with.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.