Clarity, Technology, and Solving Problems | PracticeThis.com
WP7 App with Key Windows Azure resources – Slides, Videos, How-To’s, and T-shooting – for quick consumption on the go.
This is second part following the first part, ASP.NET: Authentication With SWT Token Using Windows Azure ACS and WIF Custom Token Handler, of the overall scenario that should answer the following question:
How I can flow security context of end user through tiers between ASP.NET web app and the downstream REST WCF service?
Just published code sample on MSDN Code Gallery for the REST WCF part. Bits are here:
It largely follows the instructions available here:
Next is to connect both parts and enable the scenario of flowing the security context of end user through the tier. The challenge will be to make the original SWT token that was issued for the front end ASP.NET web app available to the backend REST WCF service. Will outline in the third and final part of these series of blog posts.
This is first part of the overall scenario that should answer the following question:
Uploaded sample code to MSDN Code Gallery that shows how to use SWT token issued by Windows Azure Access Control Service (ACS). The bits are here:
The plan is next to add another Visual Studio Project to the solution based on the following walkthrough:
The idea is simple – create one relying party in Windows Azure ACS and share the issued SWT token between the ASP.NET app and REST service. The challenge here is that WIF does not come with ready to use SWT token implementation and SWT token handler. To solve this scenario the code sample implements custom token handler, cannibalized from the following sample:
Just added another scenario to the Cloud Identity Scenarios and Solutions for Developers including solution approach, code sample, walkthrough . Courtesy of Todd Foust who created it all from scratch. The scenario is distributed application with ASP.NET web app calling to the back end WCF (SOAP) web service. Users are authenticated using Windows Live ID. End user’s security context needs to flow down to the WCF service.
Custom STS using WIF and ACS are used to solve this scenario, read the whole story here - ASP.NET Relying Party to WCF (SOAP) Relying Party Delegation With Windows Live ID