DMZ authentication scenario with AD-LDS or RODC


hello!

i'm trying find best solution following scenario:

a customer wants authenticate ad-users via ldap in application hosted in dmz. have read lot adlds , came following options.

first option: seems fit adlds , adamsync:

application - adlds - |firewall| - adds

but password should in sync too... as "small" customer, there no fim password sync ect.

second option: thought using proxyuser, requires adlds server member of domain, right? - lot of fw-ports opened. seems not best solution me.

the third option i thought using , rodc (in dedicated site) on the internal network , open 636 ldap authentication.

application - |firewall| - rodc

seems better solution proxyuser method.

so there 2 options

- option 1: authentication adlds , principal authentication (simple bind), , going different user passwords external , internal.
- option 3: rodc in internal network

any advice here? option choose? 



hi

 i recommend you use rodc scenario.also configure rodc on dmz,and configure rodc , application necessary ports on dmz,

 finaly configure necessary ports rodc between internal , dmz.this useful , more secure.

check designing rodc

https://technet.microsoft.com/en-us/library/dd728028%28ws.10%29.aspx?f=255&mspperror=-2147217396#ad_rep



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...