"Shibbolising" ASP .Net application(s)

[Peter Schober]

* Gilles Badouet <badouetg at uni.coventry.ac.uk> [2013-07-26 11:31]:
> >That generally means you will have a lot of trouble ripping out or routing
> >around existing behavior.
> 
> Why? I note that I  don't have necessarily to associate the
> Shibboleth base authentication to the existing authentication
> system. I have nothing to do with the existing authentication box. I
> got the application library and what I have to do is to experiment
> the Shibboleth authentication system within another box and
> indepently on the existing authentication.

You can setup and pla with Shibboleth on another box all day.
It just will have nothing to do with the thing you asked about.

> I am confused by what scenario to follow because I havent seen in
> the related wiki page
> (https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPEnableApplication)
> which files and which elements to configure.I just know that I have
> to place the application in "secure" folder. 

No. You can protect any resource on he webserver you want, "/secure"
is merely an example.

> I also read that 'Request Headers' is the only integration mechanism
> supported by IIS/ ASP .Net applications and don't understand how
> and where to apply it.

That means you would have to modify whatever application you want to
integrate with and make your integration code get information about
the preauthenticated subject (and its attributes) from HTTP Request
Headers which the Shibboleth SP sets automatically (based on the data
recieved and mapped from the SAML assertion recieved from the IdP).

> I would like  to know  what files and elements I should configure
> regarding  my environment (IIS)  or a link describing an ASP .NET
> integration example.

https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPEnableApplication
and the very end of the page
https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPAttributeAccess#NativeSPAttributeAccess-Tool-SpecificExamples
-peter