Реализация LDAP с ASP.NET MVC3

iptables блокирует доступ, прежде чем он достигнет приложения, тогда как hosts.allow/hosts.deny является частью PAM и требует, чтобы приложение реализовало проверку PAM и правильно обработало файл. Оба полезны, и имеющий в распоряжении обоих еще лучше.

0
задан 23 May 2012 в 19:45
1 ответ

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.

0
ответ дан 24 November 2019 в 11:39

Теги

Похожие вопросы