A Guide to Claims-Based Identity and Access Control 2nd Edition – Code samples

Language:
English
These samples illustrate with running examples the scenarios covered in the book “A Guide to Claims based Identity and Access Control, 2nd Edition".
  • Version:

    2.0

    File Name:

    Identity Guidance V2.Source.Exe

    Date Published:

    9/12/2011

    File Size:

    9.0 MB

      These samples illustrate with running examples the scenarios covered in the book “A Guide to Claims based Identity and Access Control, 2nd Edition”. To check for software prerequisites needed to run the samples, run CheckDependencies.cmd in the sample scenarios folder once all content is extracted to your local file system. This batch file launches a dependency checking tool that reports any components that are missing in your system, and it provides links if needed for obtaining, installing and configuring the missing components. Not all of samples require the same components to run, but they all need Windows Identity Foundation and IIS.Some infrastructure is shared by all of samples. For example, all of the samples use the same security token issuers for the fictitious companies that participate in these scenarios. The issuers simulate the behavior of a production issuer. The goal was to simplify the deployment experience and make it possible to run the sample applications on a single developer machine. For production applications, it is recommended that you use ADFS V2.0.
  • Supported Operating System

    Windows 7, Windows Server 2008 R2, Windows Vista

      • .NET Framework version 4.0
      • Visual Studio 2010 Ultimate, Premium, or Professional edition
      • Windows Vista, Windows 7, or Windows Server 2008 R2 (32 bit or 64 bit)
      1. Click the ‘Download Now’ link to commence the download.
      2. Save the file to your hard drive.
      3. The samples are packaged as a self-extractable zip file. When run, you’ll have to accept the End User Licensing Agreement to proceed.
      4. After accepting the license, files will be extracted to chosen destination.
      5. Each scenario has its own Visual Studio solution that will open all relevant projects.
      6. You can use the “CheckDependencies” batch file to identify potential missing components in your system.
      7. Open “readme.htm” file for details.