There is currently a discussion how and if a browser should indicate the presence of installed id selectors. I am against "polluting" the user-agent string. Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506) This indicates only that .NET3 is installed, it does not tell the relying party whether CardSpace is active or disabled. I prefer that the id selector adds a HTTP header e.g. "X-ID-Selector" to the HTTP requests. This is easy to implement;

While investigating the issues described in my former post I began to wonder why this all has ever worked... You had this feeling in your computer science life too now and then, right? My personal history regarding this is: Chuck designed the code of the openinfocard id selector in a way that it worked with early relying parties according to the examples given in THE GUIDE . Our relying party at xmldap.org is designed excactly along the examples from the guide. When I joined the team I did not have