"Shibbolising" ASP .Net application(s)

[Cantor, Scott]

On 7/24/13 4:49 PM, "Gilles Badouet" <badouetg at uni.coventry.ac.uk> wrote:

>I have just acquired 3 ASP. Net applications and want now to test my
>implementation with one of
> the applications first, which already has an authentication system
>handled by SQL server 2008.

That generally means you will have a lot of trouble ripping out or routing
around existing behavior.

>  I plan afterward to test the implementation with all the 3
>applications. 
>What is the good approach/scenarios to intergrating ASP .Net
>application(s)? I read the wiki docs, but still confused with where to
>start.

There is no such thing as "make a .NET app work". Every application is
different, apart from following various good and bad patterns of design
that are common. The integration depends entirely on the application and
how it works.

The only thing the SP does is what it's documented to do, and the wiki
describes integration patterns that are of general interest. The rest is
not something that can be turned into a recipe.

Unless you explain what you're confused by, there's nothing else I can say.

>On the other hand, I would like to know if there is any method to
>customize the login page, logout page...without requiring to update the
>installation of the IdP.

The IdP is in control of that, that's not up to the SP.

> Or How to update that installation while keeping unchanged the already
>configured metadata,
> IdP credentials and other files?

Updating it or rebuilding the warfile after changing something has no
impact on any of that.

-- Scott