Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Windows Azure Active Directory is a good option for single sign-on, but it does not <em>have to</em> be used with ACS, as can be seen here</p> <p><a href="http://msdn.microsoft.com/en-us/library/windowsazure/dn151790.aspx#BKMK_Connecting" rel="nofollow">http://msdn.microsoft.com/en-us/library/windowsazure/dn151790.aspx#BKMK_Connecting</a></p> <p>The advantages of ACS are that</p> <ol> <li>It can be used to perform claims transformation without having to write any code (e.g. in a custom ClaimsAuthenticationManager). You will not be able to handle complex transformations, but simple ones are fine.</li> <li>It can provide federation with multiple identity providers, so if you users would rather use Facebook, instead of your WAAD, it is more flexible.</li> </ol> <p>However, on the down side</p> <ol> <li>It is more complex to configure and is another moving part in your solution that can go wrong</li> <li>ACS namespaces are tied to a single Azure region so a failure in a data centre will be harder to recover from</li> </ol> <p>I had to use ACS with WAAD in a previous application I worked on because (for some reason) the <a href="http://msdn.microsoft.com/en-us/library/dd470175%28v=vs.108%29.aspx" rel="nofollow">ASP.Net MVC anti-forgery protection</a> relies on a claim of type</p> <pre><code>http://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider </code></pre> <p>which is <em>not issued</em> by WAAD. I used a simple claim transformation rule in ACS to transform the WAAD issued claim of type</p> <pre><code>http://schemas.microsoft.com/identity/claims/identityprovider </code></pre> <p>into an equivalent claim of type</p> <pre><code>http://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider </code></pre> <p>This was the only way I could think of to fix my issue at the time so it made it worth using ACS in my case. I never found out whether you could do this purely with WAAD (maybe using the graph API) because of time pressures on the project at the time.</p> <p>In answer to the extra question in your comment, there is no way to replace the sign-on page if you are using WS-Federation or OAuth 2. A crucial point of those approaches is that the user only enters their credentials into the (trusted) UI provided by the identity provider. I think you can replace the image with one of your own though. Maybe you could gather the users credentials with your own UI and get a token using the WS-Trust endpoint, but this would not give you genuine web SSO in the sense that the sign-in session would not be automatically flowed between your different web applications.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload