So I have Vista RTM running since more than a week now, however until now I haven't come across any MSFT (not to mention other corps) that are supporting CardSpace. How will MSFT try to convince people using this technology if they themselves not using it on RTM Or did I miss a site that does support it
Any MSFT website supporting CardSpace at all ?
Hot Topic
- Integration with VS2005 IDE
- Designer unable to load .xolm files
- overload methods in WF
- tableadapter update inside failed transactionscope doesn't rollback the datatable
- Can we get a sticky post?
- Dynamic interface to workflow
- RMTool problem
- MBS Navision 4.00 compatability problems
- Running non elevated process from elevated process
- Stop excution of composite activity but not terminate parent workflow!
Windows Vista
- Where is the definitive post-beta ASP.NET Workflow Sample or Walk-through?
- Expense Reporting example and DesignerTheme reference errors
- Binding of reference type property to activity/workflow member.
- Laptop close lid, and re open lid, Vista wont resume, screen is off/black
- Simple SM Workflow Action Doesn't Seem Possible... Need Help
- Creating managed cards problem
- Glass with MDI apps
- [RTM Vista] - Problem binding an ssl certificate to an ip:port, nothing works :-(
- Official Release Date?
- Serialize a cookie container
Any MSFT website supporting CardSpace at all ?
mihooper1
It is not something that as a whole, we can just turn everything on, and have support on our websites.
It was necessary to ship the client (Windows CardSpace) before we could get adoption moving. While you don't see any sites right this moment, we have work going on all over the place, and as we proceed into the future, these websites will begin supporting CardSpace for authentication.
Given the radical changes that this means to the way we interact with websites and how our identities are leveaged, slow adoption is better than 'flipping the switch' and making mistakes.
Additionally, we have been spending a good sum of time in the Usability labs identifying what works, what doesn't how the website needs to interact with the user, and what effects this has on the average Joe. You will begin to see fruits of these labors as time goes on.
g
Garrett Serack | Program Manager |Federated Identity Team | Microsoft Corporation
blog:http://blogs.msdn.com/garretts