Training content based on our guides has been as popular as the content itself. You can now download the “Release Candidate” for labs corresponding to the new guide . The labs are more than just a mirror of the guide. We took the opportunity of adding a few things that complement and extend what is explained...

The entire book is now available for browsing online on MSDN here: http://msdn.microsoft.com/en-us/library/ff359115%28lightweight%29.aspx Now, to be honest, it doesn’t look as nice as the printed book (small preview here):     But everything is in there! (and doesn’t look that bad at all either...

In synch with the availability of ADFS V2.0 Release Candidate , I’m very happy to announce that we are posting a new update of the guide. Our own “RC”. You’ll find new samples and new chapters. Both content complete now. We are now covering the following scenarios: Single Sign on for web applications...

Yesterday, we uploaded a new release of the Guide and the samples. You can download the content from here . (Note: if you downloaded them yesterday, you might want to check again. We mistakenly uploaded the samples with no docs. It is fixed now). You’ll find: Updated introduction & WebSSO chapters...

Now that we presented the scenario & the requirements , let’s take a look at the solution. What is conceptual solution we propose? Fabrikam Shipping in the pre-Claims era: This diagram shows Fabrikam Shipping today if used by Adatum (no claims, no federation): You will see the usual suspects for...

Once again, thanks everybody that wrote us with reviews, feedback and suggestions! Please keep it coming! Also: we hope to have soon a CodePlex site where we can start sharing more. We are still working out some details. As usual, the Disclaimer: this post and the next ones are early drafts to share...

Disclaimer: this post and the next ones are early drafts to share with you the direction we are taking. They might (and I hope they will) change quite a bit in the actual Guide! We might end up not covering one of these scenarios in the book. These posts represent my ideas and not those of my employer...

When we implemented claim based authorization in LitwareHR, we had to write a lot of code and play with non-trivial configurations (LitwarehR includes 2 STS and all the supporting infrastructure for securing the web services and the callers to them). Not being a security expert myself, I found the “theory”...