Java, .NET, and OpenSSO walk into a bar... The Whalphin Chronicles

Okay, okay.  I know the title and tag line sounds like the opening of a bad joke.  But someday I'll blog about it.  Let's just say it has to do with the fact that I'm playing with multiple technologies.  But I digress, the real meat of this entry is about the Fedlet for .NET provided by OpenSSO.

So, let me provide a sneak preview of the upcoming Fedlet for .NET for the OpenSSO community.  Back in December, Rajeev created a prototype of a Fedlet for the .NET community.  I was chartered with continuing his efforts by providing an API for .NET developers to obtain subject and attributes from a SAML2 response received after successfully authenticating with an Identity Provider (IDP).  Ready to play?

Steps to prepare...

1. Create a Hosted Identity Provider along with Circle of Trust.  This can be done from the OpenSSO Common Tasks page.
2. Create a Fedlet for the soon-to-be-installed Sample Application.  This can also be done from the OpenSSO Common Tasks page.  For the Sample Application, you'll want something similar to http://sp.example.com/SampleApp.   Optionally add attributes so you can see them come over after successful authentication later on.
3. Edit the HTTP-POST location for the newly Fedlet (aka Service Provider) to append the ".aspx" suffix.  This can be done by navigating to the Federation tab and then editing the Service Provider > Services > HTTP-POST location (for example:  http://sp.example.com/SampleApp/fedletapplication.aspx)
   
4. Extract the metadata files within the generated Fedlet.zip file for later use below.
   

To try it out...

1. Download the SampleApp.zip file.
2. Unzip the contents to a temporary location.
3. Copy the metadata files obtained from the Fedlet.zip mentioned above over the files within the SampleApp/App_Data/ folder.
   
4. Within Internet Information Server, create a virtual directory with the SampleApp/ folder found within the unzipped folder.
1. IIS 6 has Add Virtual Directory.  Be sure to have Read and Script permissions set for the application.
2. IIS 7 has Add Application with no additional options required to be altered.
5. Access the Sample Application (for example:  http://sp.example.com/SampleApp)
   

It's still a work in progress but hopefully all went well and you're looking at a Sample Application reiterating the above steps as well as a link to demonstrate the functionality.  Let me know either way.  Feedback is always welcome.