Exercise 1: Use Access Control Service for Accepting Users from Multiple Identity Providers
In the first exercise you will familiarize with ACS’ basic settings and terminology. Your task is to secure access to a newly created ASP.NET Web site. The Web site will accept users from Google, Yahoo! and Windows Live ID. As you will see in a minute, ACS makes it real easy.
Task 1 – Creating the Initial Solution
Task 2 – Signing-up for Windows Azure AppFabric Access Control Service and Creating the Service Namespace
You are now going to subscribe to ACS.
Task 3 – Configuring the Allowed Identity Providers, the Relying Party and the Signing Certificate
Task 4 – Configuring a Website to Accept Tokens from Access Control Service
Exercise 1: Verification
It’s time to give your newly secured Web site a spin. In order to verify that you have correctly performed all steps in exercise one, proceed as follows:
Exercise 1: Summary
In the first exercise you learned the ropes of using ACS for handling authentication for you. At the same time, you learned how to use WIF for automatically configure a Web site to outsource authentication to external entities. The process is exactly the same whether you point your application to ACS, an internal identity provider such as ADFS2, and any product complying with WS-Federation.
Once you outsourced authentication to ACS, you can start changing settings (such as which identity providers should be used) directly at the ACS portal without the need to touch the application code.