Note that there are some explanatory texts on larger screens.

plurals
  1. POASP.NET MVC 2 and authentication using WIF (Windows Identity Foundation)
    primarykey
    data
    text
    <p>Are there any decent examples of the following available:</p> <p>Looking through <strong><a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=c148b2df-c7af-46bb-9162-2c9422208504&amp;displaylang=en" rel="noreferrer">the WIF SDK</a></strong>, there are examples of using WIF in conjunction with ASP.NET using the <code>WSFederationAuthenticationModule (FAM)</code> to redirect to an ASP.NET site <em>thin skin</em> on top of a Security Token Service (STS) that user uses to authenticate (via supplying a username and password). </p> <p>If I understand WIF and claims-based access correctly, I would like my application to provide its own login screen where users provide their username and password and let this delegate to an STS for authentication, sending the login details to an endpoint via a security standard (WS-*), and expecting a SAML token to be returned. Ideally, the <code>SessionAuthenticationModule</code> would work as per the examples using <code>FAM</code> in conjunction with <code>SessionAuthenticationModule</code> i.e. be responsible for reconstructing the <code>IClaimsPrincipal</code> from the session security chunked cookie and redirecting to my application login page when the security session expires.</p> <p>Is what I describe possible using <code>FAM</code> and <code>SessionAuthenticationModule</code> with appropriate web.config settings, or do I need to think about writing a <code>HttpModule</code> myself to handle this? Alternatively, is redirecting to a thin web site STS where users log in the de facto approach in a passive requestor scenario?</p>
    singulars
    1. This table or related slice is empty.
    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.
 

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