By Daniel Bartholomew on 3/15/2008 5:08 AM

Currently DotNetNuke supports the use of personal cards when using CardSpace and the Identity Metasystem. This is a step forward in terms of dealing with up and coming digital identity management.

In its current form CardSpace cannot support holding a user's custom profile attributes as a personal card is locked down to just a few pieces of information.

This is going to change. I've just started implementing a Secure Token Server for DotNetNuke based on the newly announced sharpSTS project.

Soon, you'll be able to issue your own managed cards through DotNetNuke, which include all the users personal information. I'm also going to write a new provider for DotNetNuke that will allow webmasters to declare what information they should save in their databases.

As a webmaster you'll be able to offer your customers all the personalisation they expect, while offloading privacy and security concerns.

If you are ... Read More »

By Daniel Bartholomew on 3/10/2008 6:35 PM

Recently the CardSpace Authentication Provider for DotNetNuke was released to the public.

In its current form the Authentication Providers requires your server to have the .NET Framework 3.0 installed.

It also requires you have an SSL certificate, as the CardSpace client will only by activated on a users computer when the browser connects to the sign in page using HTTPS. This limitation has been removed in .NET 3.5 - and we are currently working on an updated release to allow non-HTTPS CardSpace authentication.

Furthermore, you'll need to grant your ASP.NET Process's Identity Account permissions to read the private key of your SSL certificate. More information about completing this task can be found here: http://trac.dbartholomew.net/wiki/DotNetNukeCardSpaceAuthenticationProvider