Welcome to the second walkthrough of the new WIF tools for Visual Studio 11 Beta! This is about using the tools to modify common settings of your app without editing the web.config.
The complete series include Using the Local Development STS, manipulating common config settings, connecting with a business STS, get an F5 experience with ACS2.
Let’s say that you downloaded the new WIF tools (well done! ) and you went through the first walkthrough, and you are itching to go deeper in the rabbit’s hole. Pronto, good Sir/Ma’am!
Let’s go back to the tool and take a look at the Configuration tab. What’s in there, exactly?
In V1 the tools operated in fire & forget fashion: they were a tool for establishing a trust relationship with a WS-Federation or WS-Trust STS, and every time you opened them it was expected that your intention was to create a new relationship (or override (most of) an existing one).
The WIF tools for .NET 4.5 aspire to be something more than that: when you re-open them, you’ll discover that they are aware of your current state and they allow you to tweak some key properties of your RP without having to actually get to the web.config itself.
The main settings you find here are:
Those are of course the most basic settings: we picked them because how often we observed people having to change them. Did we get them right? Let us know!
Don’t forget to check out the other walkthroughs: the complete series include Using the Local Development STS, manipulating common config settings, connecting with a business STS, get an F5 experience with ACS2.
Checking the RequireHttps seems to have no difference on the LocalSTS.exe hosting URL. I was assuming it will host the STS on a Https endpoint.
Is there any way to host LocalSTS.exe on a HTTPS endpoint.
The July2012 Identity Training Kit's lab ACS2Federation tries to configure LocalSTS.exe as an IdP in ACS, but it fails as ACS expects all IdPs to be available on https endpoints.