Hands-on Lab 1

The objective of this hands-on lab is to create an on-premisses ASP.NET web application (relying party) that consumes identity information from an already configured federation provider in Windows Azure’s Access Control Service. This service will, in turn, consume identity information from Google or Facebook.

Objective

Sections:

  1. Create Relying Party’s web application
  2. Configure IIS for the web application
  3. Configure a HTTPS endpoint
  4. Configure the web application to use federated identity
  5. PowerShell

1. Create Relying Party’s web application

At the end of this section, you should have an ASP.NET web application, ready to be changed to use identity information from an external provider. Visual Studio comes with templates that generate an example site with several pages that is enough for this HOL.

2. Configure IIS for the web application

At the end of this section, you should have the ASP.NET web application configured on IIS, served through an HTTP endpoint. This is the first part of IIS configurations to have the application ready for changes related to identity federation.

3. Configure a HTTPS endpoint

At the end of this section, you should have the ASP.NET web application being served through an HTTPS endpoint. This is the last part of IIS configurations before changes related to identity federation.

4. Configure the web application to use federated identity

At the of this section, you should have the ASP.NET web application created in the previous section using federated identity.

5. PowerShell

The previous steps can be automated using PowerShell and command-line tools with, for example, the following commands: