Tag: patterns & practices

I’m happy to announce the next p&p Symposium here in Redmond. Details below. The patterns & practices Symposium is the event for software developers and architects to have engaging and meaningful discussions with the people creating technologies and guidance at Microsoft. This year’s Symposium topics span the spectrum of…

Update: the same roadmap is now published on MSDN. I adjusted the slide below to make timelines clearer. No other changes. We wanted to share with you all the projects we are either working on or we have identified as potential areas of investment in the current Fiscal Year (that started past July and ends…

This week, we completed a small PoC for brabant court, a customer that is building a Windows Azure application that integrates with Intuit’s Data Services (IDS). A couple words on mabbled from brabant court. Mabbled is a Windows Azure app (ASP.NET MVC 3, EF Code First, SQL Azure, AppFabric ACS|Caching, jQuery) that provides complementary services…

In the previous post I covered the “semi-passive” way for authentication between a Windows Phone 7 client and a REST service. This post completes the information with the “active” way. There’s nothing unexpected here really: We call the Identity Provider using a RequestSecurityToken message (RST) We send the SAML token to ACS and get a…

In the last drop, we included a sample that demonstrates how to secure a REST web service with ACS, and a client calling that service running in a different security realm: In this case, ACS is the bridge between the WS-Trust/SAML world (Litware in the diagram) and the REST/SWT side (Adatum’s a-Order app) This is…

Second drop of samples and draft chapters is now available on CodePlex. Highlights: All 3 samples for ACS v2: ("ACS as a Federation Provider", "ACS as a FP with Multiple Business Partners" and "ACS and REST endpoints"). These samples extend all the original "Federation samples" in the guide with new capabilities (e.g. protocol transition, REST…

Apprenda’s SaaSGrid is now “claims enabled”! This is fantastic news. Any SG customer can now enjoy the benefits of claims based identity: simpler user management, easy federation with business partners, support for multiple identity providers, greater interoperability, etc. SG support for claims based identity maps nicely with what’s described in the “Claims Identity Guide –…

Following up on previous post, there were 2 questions: Where do these green checks images come from? There are nowhere in a-Order or in a-Expense… you would spend hours looking for the PNG, or JPG or GIF and you will never find it, because it is very well concealed. Can you guess where it…

While reviewing all the existing samples we’ve noticed that our implementation of Single Sign Out was kind of….weak. It wasn’t really fully implemented and wasn’t very clear what was happening either (or what it should happen) We’ve fixed all that now in scenario 1: WebSSO. Things get more complicated when more than 1 STS is…

To work properly, a-Order needs a number of claims to be supplied: User name Organization Role The "Organization” claim is used to filter orders belonging to a specific customer of Adatum. For example, Litware users (like Rick) will eventually end up with a token containing a claim with “Organization=Litware”. All this is done in step…