- Joined
- Feb 29, 2008
- Messages
- 4,093
- Likes received
- 37
- Thanks received
- 16
- Location
- In my homie
Thankyou for your answers. Unfortunately I can't use VPN as the requirement is very adhoc access among a large user base.
My main concern really is the implication of the ASP.Net application being in DMZ & communication with AD from there. I would think that there would need to be some extra configuration to get this to work. DMZ machine isn't in a domain. I will try the url that was recommended for asking this question.
SSL VPN is a clientless solution and would be absolutely ideal for you environment. However, if your client has accepted the risk for not securing the transmission of developer code and AD authentication over the interweb, then fair enough. However, if I were you, I would give the client the option and advise them of the insecurities of doing non-encrypted uploads of code (i.e. 3rd-party interception, modification, etc. etc.) before you dismiss SSL VPN from the equation. Let them make the decision to take the risk, otherwise the risk may be transferred to you and you could be liable for any loss incurred by the client.
