I thought that my Live Labs Managed Card was missing claims, which was preventing the CardSpace UI from sending the card to the site.

Turns out that I was using the wrong token type - so far my self issued cards have been using SAML 1.0 tokens, whereas the Live Labs STS required SAML 1.1 tokens.

I've updated my system to allow the TokenType to be configurable, so now you can choose the token type for each DNN portal.

Managed Cards are still not ready, I'm waiting on an update of the TokenProcessor from Microsoft that will allow the Live Labs STS cards to be used.

Stay posted..

I've create a child portal in this DotNetNuke installation to test the use of CardSpace with Managed Cards.

At this stage the implementation of the DNN portal has gone well. The portal specifies that it requires a managed card that has been issued by the Microsoft Live Labs STS.

Unfortunately, the cards that are created by the Live Labs STS user interface do not seem to be complete. The sample website that you can download from the Live Labs STS shows that the PPID and the nickname are required claims. The two cards that I've generated from the site do not contain these claims, therefore I cannot send them to the child portal.

I've got an email off to the team at the Live Labs STS site, and I hope they can point out exactly what's gone wrong here. So, stay tuned..

I've extended the DNN CardSpace module to accept managed cards. I'll have a demo environment set up over the weekend that will allow you to use managed cards from the Microsoft Live Labs STS.

Eventually, this will allow a DotNetNuke installation to allow registration and sign in from a Microsoft Live Id - or any other managed information card.

Unfortunately my hosting provider had a problem with my SSL certificate, and the secure pages on my site were unavailable for a day.

This prevented the login and register pages from showing.

If you tried to use my site to test the CardSpace DNN modules and you were unsuccessful please try again, hopefully there won't be any more issues with the server.

In the past couple of days since I announced that the CardSpace module for DNN was available, I've had 24 new users.

I haven't promoted of the module very hard, and there have been very few problems with the system.

I've taken the forum offline as blog comments seem to do the job.

Over the next week I'll harden the module and write a list of known issues.

I've got the CardSpace DotNetNuke modules ready for testing on this site.

My Readify peer, Philip Beadle, has successfully tested them for me, I'm looking for as many testers as possible.

If you have CardSpace installed on your computer, can you please register and login to the site and post into the forums information about your experience, and any feedback.

I've successfully overcome the "Keyset does not exist" error that I was getting from CardSpace.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=887903&SiteID=1

Garrett Serack's command line functions at the bottom of the post are the key to the solution.

I've been waiting on WebHost4Life, my Internet Host, to update the web server to handle CardSpace.

Initially, I purchased their $40USD SSL certificate. This took a couple of days to handle.

Then, after my CardSpace code executed, I realised that the server I'm using didn't have .Net 3.0 libraries installed. This took another day to install.

Then I got the error "Keyset does not exist", it looks like this is because I missed some steps in the SSL certificate installation. More information is given here.

Also, during this process, I upgraded my DNN installation to include ssl_Module from www.snowcovered.com. This will allow me to ensur ...

I've finished a first cut of CardSpace modules for DotNetNuke. Over the next couple of days they will be installed on this site for public demonstration and testing.

At the moment these modules do not allow users to create an account in DNN with an Information Card.

If you use the standard DNN process for creating your user account you can login to this site and link your Information Card to your DNN account.

After that, when you return to the site, you can provide your Information Card to sign in, or use standard DNN login mechanisms.

On my journey of implementing CardSpace into DotNetNuke I came across this exception: "That assembly does not allow partially trusted callers."

It seems that System.IdentityModel or System.ServiceModel doesn't like that DotNetNuke is set to run under medium trust by default.

I've set DotNetNuke to high trust for my development, we'll see how this pans out.