Authentication in WP7 client with REST Services–Part II

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…


Authentication in WP7 client with REST Services–Part I

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…


A year’s balance–next project

A little bit late for a year balance since the year has already started, or so I’m told. Anyway, as we prepare for the next project, I reflected on my team’s work for the last 18 months. 18 months is more than a year, so you might wonder why am I doing a year balance…


Tailspin Surveys Mobile – An early screenshot

Our dev team is fearlessly building the first versions Tailspin Surveys Mobile. Here’s an early example of their work: Now we are talking, huh?


Tailspin Surveys–Windows Phone 7 edition–A guide to the Guide

  As adopted in all our recent guides, here’s a quick map for the entire “Windows Phone 7 Developer Guide” . No promises of course on the final scope. We might end up merging some chapters, deleting some other, etc. But this is our current intent. Feedback very welcome!


Tailspin Surveys–Windows Phone 7– UI Mockups

Here’re some initial sketches of how Tailspin would look like and the navigation patterns we want to implement: Navigation: Home will list all available surveys to this particular user. Take Survey, allows to start one particular survey from the home page. Many can be taken at the same time. Survey Details shows metadata about a…


Tailspin Surveys–Windows Phone 7 edition

Here’s a high level overview of the major components we are planning for Talspin Surveys. A few notes: The backend is essentially an extension to Tailspin surveys as described an implemented in the Windows Azure Architecture Guide (Part 2). There’s now a new services head (an OData/JSON API) that is used by the devices. Tailspin…


What’s next? Tailspin goes mobile…

Now that the Windows Azure Architecture Guide – Part 2 is “done” (Done = content is complete and production is taking place. Production = index, covers, PDF conversion, etc), our team is ready for the next adventure. Our fictitious ISV, Tailspin, is very innovative and wants to stay on the latest and greatest. Now they…