WCF: WS-* Federation HTTP Binding (WSFederationHttpBinding)...

I haven't forgotten to follow up on federated security and WCF. Indeed, it's been quite fun and interesting digging around in it before I do any more write-ups on it.

What I thought was going to be a two-part piece on WSFederationHttpBinding will in all likelihood be a four-part piece.

WCF: WS-* Federation HTTP Binding (WSFederationHttpBinding), Part 1
Part 1 is an overview and is can be found here.

WCF: WS-* Federation HTTP Binding (WSFederationHttpBinding), Part 2
This will cover installing, configuring, and managing a security token service (STS). In the real world, this will probably have already been done by the time you consider WSFederationHttpBinding. (If you have ActiveDirectory, for instance, you're pretty much already done.) But, for the purposes of having something we can play with, we'll need to find, install, configure, and use a simple STS.

WCF: WS-* Federation HTTP Binding (WSFederationHttpBinding), Part 3
With part 3 we'll look at connecting all three components -- the service, the client, the STS -- together into one (hopefully, smooth-running) shebang.

WCF: WS-* Federation HTTP Binding (WSFederationHttpBinding), Part 4
Part 4 will be dedicated to some tips, techniques, and other customizations we can use to make life easier, more robust, and more secure.

Comments

Post a Comment

Popular posts from this blog

Using Reference Aliases

Image
I recently ran across a situation where two different libraries shared identical namespaces and class names. Visual Studio complained anytime I used one of these classes that it was an ambiguous reference. I needed both libraries -- each contained some unique elements -- so I couldn't ditch one or the other. But, as I said, anytime I tried to use a class that was common (again, via the class name and namespace), I received the ambiguous reference error. This was a real problem, so say the least. However, C# provides a way to specify exactly which library (reference) you mean when you use an object that's common to two or more libraries. Simply put, you use an extern alias  statement. The concept is fairly simple: Give the reference an alias (I used the Properties windows for the reference). Add an extern alias statement, putting it before your using statements. Add a using statement, which effectively links a specific object through the extern alias statement to th
Read more

List of Visual Studio Keyboard Shortcuts

Here's a link to a great list of keyboard shortcuts for Visual Studio: 149 Shortcuts for Visual Studio 2015 (Windows) While there's no need to memorize the list (that's why someone has created a cheat sheet, after all), it certainly doesn't hurt to look over the list from time to time and try to add one more command to your repertoire.
Read more