Here goes everything to do with trying out the pre-RTM bits. Build links, tips, bugs, pointers to samples, etc.
What you need to run Windows CardSpace On the client you will need to install .NET Framework 3.0 and for browser applications that support information cards you will need a web browser (
e.g. IE7 Beta 2 or 3) that recognizes the "application/x-informationcard" object tag. When you have installed .NET Framework 3.0 you will see the Digital Identities applet in the Control Panel.
On the server, if you're building a Relying Party you need an SSL certificate plus a way to publish your security token policy and code to process tokens. WCF and the CardSpace classes are an easy means to accomplish this (check out the samples and follow the tutorials) but you can use any technology you like that understands certificates and Web Services. If you're building an Identity Provider you need an SSL certificate, a security token service (i.e. an implementation of WS-Trust) and a way to create information cards for your users. Again WCF and the CardSpace classes provide the means to do this so check out the samples and tutorials.
Going from NetFX 3.0 Beta 2 to June CTP
The CardSpace card schema and store format change between Beta 2 and June CTP so please be aware that any cards you create using Beta 2 will have to be recreated rather than simply imported when you move to later builds.
Browsers that work with Windows CardSpace
Internet Explorer 7.0 Beta 2 or Beta 3 - You need at least IE Beta 2 to get the browser samples to work.
Firefox, Opera and Safari - You'll need a plug-in to recognize the "application/x-informationcard" tag, call into the CardSpace system and post the resulting token to the Relying Party website
Differences between IE 7 Beta 2 and IE Beta 3
There is a difference in how you need to delimit claims in HTML targetting IE 7 Beta 2 and Beta 3. Beta 2 uses a comma as the delimiter between claims, Beta 3 uses a space as the delimiter (the comma is a valid character in a URL so should not be used).
How to delete the CardSpace store
Obviously you will lose all information in the store if you do this so back up your cards first. The store will be re-created the next time you launch CardSpace.
1) Log in as an administrator
2) Take ownership of c:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\InfoCards
- Right-click on the folder
- Click the Security tab. Click OK on the error dialog
- Click the Advanced button
- Click the Owner tab
- Replace the owner on subcontainers and objects
3) Delete the Folder
How to see what's in a card
This helps you to understand how CardSpace works. Simply create a Provider card using the Managed Card Creator tool (or any other tool that creates a Provider card), rename the extension from .crd to .xml and then open up the file in Internet Explorer. You will see that a card is just a signed chunk of XML with all the token metadata in it.
Turning on tracing
This is what you need to put in your config file. <PATH> should be replaced by the directory path you want to use.
<configuration>
<system.diagnostics>
<sources>
<source name="System.ServiceModel.MessageLogging" switchValue="Verbose,ActivityTracing">
<listeners>
<add type="System.Diagnostics.DefaultTraceListener" name="Default">
<filter type="" />
</add>
<add name="MessageLogging Listener">
<filter type="" />
</add>
</listeners>
</source>
</sources>
<sharedListeners>
<add initializeData="<PATH>\app_messages.e2e"
type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
name="MessageLogging Listener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack">
<filter type="" />
</add>
</sharedListeners>
</system.diagnostics>
<system.serviceModel>
<diagnostics>
<messageLogging logEntireMessage="true" logMessagesAtServiceLevel="true" />
</diagnostics>
...
</system.serviceModel>
</configuration>