Geek Answers Handbook

Integrating Windows Domain Authentication with an External Web Site

I am a developer of applications with limited Internet time (SAAS), when I start, I expect that most of my clients will authenticate (log in) to my application using the standard email technique + password.

However, I would like to offer a more efficient single sign-on option for larger clients who will have ready-made communities of potential users of my system. Such communities will often run Windows desktop computers that have already authenticated against the internal corporate Windows domain controller.

I am looking for some option to improve the process of authenticating a user to a website and trusting or delegating authentication of a client’s domain. I would be a very junior partner in any such integration, so I doubt that a large corporation will allow me to launch a satellite domain controller connected to their system. Savings in SAAS will not allow the use of hardware VPNs.

The Azure cloud is likely to be used to host my SAAS application, if that helps clarify the options.

+4
source share
3 answers

Another option at your disposal is Active Directory Federation Services (ADFS). Take a look at Active Directory Federation Services (ADFS) Overview in Windows Server 2003 R2

+2
source

Since you want to host this for both small and large clients, I suggest you use Windows Azure ACS (Access Control Service) for your installation.

This allows your application to use any identity provider, such as facebook, google, live id and yahoo. ACS will also allow Active Directory federation through ADFS.

Thus, you can provide your customers with all possible options and keep the application code the same.

+1
source

Step 1: Configure one-way trust of your domain in your domain. You do this, they are not involved.

Step 2: use SSPI to obtain credentials via keberos or SSL.

0
source

More articles:


All Articles