Thankfully, Microsoft has created such a control which allows you to view the contents of the Security Token as well as the raw SAML Token that is being created.
Unfortunately, the original control was written back in November of 2009 and is therefore no longer valid for the latest release of the Windows Identity Foundation SDK. In addition, because the code is quite old, it also does not support Visual Studio 2010 (only Visual Studio 2008).
You can download the SecurityTokenVisualizer Control from here: http://code.msdn.microsoft.com/TokenVisualizerCtrl
However, once you have downloaded the control, installing it becomes the tricky part.
Before, you get started, you will need to make sure you have the following things installed/configured:
- Windows Vista/7 with IIS 7/IIS 7.5
- Windows Powershell
- Windows Identity Foundation Runtime http://support.microsoft.com/kb/974405
- Windows Identity Foundation SDK http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c148b2df-c7af-46bb-9162-2c9422208504&displaylang=en
- Visual Studio 2008 with SP1
Installing the SecurityTokenVisualizer Control
- Run the SecurityTokenVisualizerControlPDC09.Setup.exe
- Select a target location for extracting the files
- Once the extraction is complete, a Configuration Wizard will launch
- Since the Configuration Wizard was scripted a long time before the latest release of the Windows Identity Foundation SDK, it will not work. Therefore, click on the Cancel button at this time.
- Now for some manual editing.
- Look for a directory below the extracted SecurityTokenVisualizerControl called dependencyChecker
- You should find a file called Dependencies.xml
- Open up the file in a text editor of your choice and look for an element that looks like this:
title="Microsoft Windows Identity Foundation SDK"
explanation="The control requires Windows Identity Foundation SDK"
- Remove this element from the file (there should be 2 instances of it total within the file)
- Save the changes to the file.
- From within the dependencyChecker directory, you should now be able to manually launch the ConfigurationWizard.exe.
- Once all of the checks complete successfully, you should be able to proceed with the installation of the SecurityTokenVisualizer Control.
Post a Comment