Network World
Friday, January 9, 2009
DNSstuff.com
Get information about your IP
IP Information
50+ On-demand DNS and network tools

Community: Security

Navigation

CardSpace - surely another Laurel & Hardy idea from the merchants of bloatware?

"we found numerous ways that the CardSpace technologies could eventually become quite useful to the enterprise."

Enterprise use of CardSpace sums it up, why don't commentators like yourself actually point out that it's a technology beyond home users? 80% of home user's don't know what a USB drive is? And how many of those 20% could actually backup their keys generated through CardSpace, move them them between home and work and keep them in-sync?

"OpenID won't go away, of course, but it appears to be doomed as a potentially mainstream identity"

Facebook Connect sounds great, but why didn't MS Passport take off when it was opened up?

www.theregister.co.uk/2001/11/05/ms_passport_cracked_with_hotmail

With OpenID - the user get to choose their provider regardless of their moniker - portability. Why aren't the commentators highlighting that gem in OpenID?

If Facebook and certainly Twitter don't get acquired - they are going to run out of money because they don't have a sustainable business plan. Why would users choose these providers for any future dependent digital identity?

Click to read the article this is in response to.

Microsoft lover obviously

0

You are probably a M$ lover.
with a 99% penetration rate in the enterprise, there is no doubt M$ will succeed with cardspace.

What you are missing here, is that openID is not about a company, not about a group. It's about identities on the INTERNET not your local network.

and just like HTTP, the technology should be FREE and maintained by a group such as the W3C.

CardSpace/Infocard falls short on both expectations.

Kind regards,

PS: Next time, try to leverage your articles, would you ?

Err, Information Card technology isn't a Microsoft technology

0

It's a common misconception that Information Card technology is proprietary to Microsoft. In the past there there has been some truth to this, and I realize that most people think it remains true. But it isn't. Quite the contrary.

Information Card technology development started approx five years ago at Microsoft, IBM, Higgins, and a few other places. What created the perception that it was a "Microsoft" technology was a series of actions and omissions by Microsoft over the intervening years. Some were intentional, some not. Many had unintended consequences.

From early on Microsoft was focused on shipping a product as soon as possible. Although getting CardSpace to ship in Nov 2006 was a good thing, their lack of progress in other areas had consequences that worked against our common vision of creating a very vibrant ecosystem of interoperable, competing implementations based on open standards.

To some extent getting a 1.0 product out the door so far ahead of when others could ship (mostly for IPR reasons) helped create the perception that indeed this was a Microsoft dominated technology. Even little things, like for a time appropriating the term Information Card in Microsoft documents. Nor did code-naming the product, "InfoCard". Worse, it took the organization a long time to get the IP behind CardSpace released under the Microsoft OSP. Worst of all, it has only been in recent weeks that the last few remaining protocol design documents have been submitted to an SDO--in this case the new OASIS IMI TC.

Of course, Kim, Mike and others always knew that to be successful there had to be open, standard protocols and multiple competing selectors (and other IdP and RP services) running on all platforms and mobile devices. I've always felt that they saw the big picture. And I think it's fair to say that compared to Microsoft's normal modus operandi there has been unprecedented level of openness, collaboration, and good will.

And in the end, to Microsoft's credit, everything did get done. Today there are open source implementations of everything Microsoft has done (and some stuff that Microsoft hasn't yet done!) living in open source projects like Higgins, Novell's Bandit, OpenInfoCard, Pamela and others. The technology has recently gotten its own non-profit foundation (see http://informationcard.net) (ICF). The ICF and its members, with the addition of IBM, have provided most of the funding and resources for the OSIS series of interop events involving card issuing sites, selectors and relying sites (and relying apps). The one at RSA had 53 companies and open source projects collaborating together. The next and fourth one will be at DIDW.

So today, Information Card, InfoCard, I-Card (or whatever you call it) technology is open, free, and not a Microsoft proprietary technology.

-Paul

PS: Ben Laurie's voice is echoing in my head right now. How Information Card implementations work interoperably between Microsoft's Credentica-developed selective disclosure technology and the IBM Zurich Idemix technology has yet to be seen. I'd say there's reason to be hopeful. Fingers crossed.

Central questions - still not answered

0

OK, so I am not keen on MS, I'll come clean, and did assume it was a MS initiative etc.

However - would someone please answer my basic usability issues:

As I either right or mis-understand Infocard.

"Enterprise use of CardSpace sums it up, why don't commentators like yourself actually point out that it's a technology beyond home users? 80% of home user's don't know what a USB drive is? And how many of those 20% could actually backup their keys generated through CardSpace, move them them between home and work and keep them in-sync?"

Cheers Mark

How about Higgins? Looking

0

How about Higgins? Looking into Higgins and CardSpace, I am convinced that Higgins is way better. But sadly, due to Microsoft's dominance in the market, CardSpace would probably win out.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <i> <b> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <blockquote> <br /> <br> <p>
  • Lines and paragraphs break automatically.
  • You can use BBCode tags in the text.
  • Web page addresses and e-mail addresses turn into links automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

Advertisement: