Home  

Random  

Nearby  



Log in  



Settings  



Donate  



About Wikipedia  

Disclaimers  



Wikipedia





Windows CardSpace





Article  

Talk  



Language  

Watch  

Edit  





Windows CardSpace (codenamed InfoCard) is a discontinued identity selector app by Microsoft. It stores references to digital identities of the users, presenting them as visual information cards. CardSpace provides a consistent UI designed to help people to easily and securely use these identities in applications and web sites where they are accepted. Resistance to phishing attacks and adherence to Kim Cameron's "7 Laws of Identity"[1] were goals in its design.[2]

Windows CardSpace
Developer(s)Microsoft
Operating systemMicrosoft Windows
SuccessorU-Prove
Service nameWindows CardSpace (idsvc)
TypeIdentity management system

CardSpace is a built-in component of Windows 7 and Windows Vista, and has been made available for Windows XP and Windows Server 2003 as part of the .NET Framework 3.x package.

Overview

edit

When an information card-enabled application or website wishes to obtain information about the user, it requests a particular set of claims. The CardSpace UI then appears, switching the display to the CardSpace service, which displays the user's stored identities as visual cards. The user selects a card to use, and the CardSpace software contacts the issuer of the identity to obtain a digitally signed XML token that contains the requested information. CardSpace also allows users to create personal (also known as self-issued) information cards, which can contain one or more of 14 fields of identity information such as full name and address. Other transactions may require a managed information card; these are issued by a third-party identity provider that makes the claims on the person's behalf, such as a bank, employer, or a government agency.

Windows CardSpace is built on top of the Web services protocol stack, an open set of XML-based protocols, including WS-Security, WS-Trust, WS-MetadataExchange and WS-SecurityPolicy. This means that any technology or platform that supports these protocols can integrate with CardSpace. To accept information cards, a web developer needs to declare an HTML <OBJECT> tag that specifies the claims the website is demanding and implement code to decrypt the returned token and extract the claim values. If an identity provider wants to issue tokens, it must provide a means by which a user can obtain a managed card and provide a Security Token Service (STS) which handles WS-Trust requests and returns an appropriate encrypted and signed token. During the 2000s, identity providers that didn't wish to build STS could obtain one from a variety of vendors, including PingIdentity, BMC, Sun Microsystems, Microsoft, or Siemens.

Because CardSpace and the identity metasystem upon which it is based are token-format-agnostic, CardSpace did not compete directly with other Internet identity architectures like OpenID and SAML. These three approaches to identity can be seen as complementary,[3] because during the 2000s, information cards could be used today for signing into OpenID providers, Windows Live ID accounts, and SAML identity providers.

IBM and Novell planned to support[4] the Higgins trust framework to provide a development framework that includes support for information cards and the Web services protocol stack, thus including CardSpace within a broader, extensible framework also supporting other identity-related technologies, such as SAML and OpenID.

Release

edit

Microsoft initially shipped Windows CardSpace with the .NET Framework 3.0, which runs on Windows XP, Windows Server 2003, and Windows Vista. It is installed by default on Windows Vista as well as Windows 7 and is available as a free download for XP and Server 2003 via Windows Update. An updated version of CardSpace shipped with the .NET Framework 3.5. The new Credential Manager in Windows 7 uses Windows CardSpace for the management and storage of saved user credentials.[5]

Discontinuation

edit

On February 15, 2011, Microsoft announced that Windows CardSpace 2.0 would not be shipped.[6] Microsoft later worked on a replacement called U-Prove.[7]

See also

edit

References

edit
  1. ^ Cameron, Kim (2005-05-01). "The Laws of Identity". MSDN. Microsoft. Retrieved 2010-12-13.
  • ^ Cameron, Kim; Jones, Michael B. (January 2006). "Design Rationale behind the Identity Metasystem Architecture" (PDF). Retrieved 2010-12-13.
  • ^ Ernst, Johannes (January 24, 2006). "Three Digital Identity Standards". Archived from the original on August 9, 2011.
  • ^ "Open Source Initiative to Give People More Control Over Their Personal Online Information". News room. IBM. February 27, 2006.
  • ^ "Windows 7 new features". TechNet. Microsoft. February 3, 2009. Retrieved March 30, 2018.
  • ^ "Beyond Windows CardSpace". Claims-Based Identity Blog. Microsoft. 15 February 2011. Archived from the original on 12 July 2012. Retrieved 23 July 2011.
  • ^ "U-Prove Home". Connect. Microsoft. Archived from the original on July 14, 2011. Retrieved July 23, 2011.
  • Further reading

    edit
  • Nanda, Arun (April 2007). Identity Selector Interoperability Profile (PDF). Microsoft.
  • An Implementer's Guide to the Identity Selector Interoperability Profile V1.0 (PDF). Microsoft, Ping Identity. April 2007.
  • Jones, Michael B. (April 2007). A Guide to Using the Identity Selector Interoperability Profile V1.0 within Web Applications and Browsers (PDF). Microsoft.
  • Microsoft Open Specification Promise, May 2007.
  • edit
    Software development
    Identity selectors
    Blogs

    Retrieved from "https://en.wikipedia.org/w/index.php?title=Windows_CardSpace&oldid=1189846327"
     



    Last edited on 14 December 2023, at 11:21  





    Languages

     


    العربية
    Deutsch
    Français

    Nederlands

    Русский
    Українська

     

    Wikipedia


    This page was last edited on 14 December 2023, at 11:21 (UTC).

    Content is available under CC BY-SA 4.0 unless otherwise noted.



    Privacy policy

    About Wikipedia

    Disclaimers

    Contact Wikipedia

    Code of Conduct

    Developers

    Statistics

    Cookie statement

    Terms of Use

    Desktop