Information Card

From Wikipedia, the free encyclopedia
Information Cards shown in Windows CardSpace Identity Selector
Information Cards shown in DigitalMe Identity Selector

Information Cards are personal digital identities that people can use online, and the key component of Identity metasystems. Visually, each Information Card has a card-shaped picture and a card name associated with it that enable people to organize their digital identities and to easily select one they want to use for any given interaction. The Information Card metaphor is implemented by Identity Selectors like Windows CardSpace, DigitalMe or Higgins Identity Selector.

The Identity Metasystem is an interoperable architecture for digital identity that enables people to have and employ a collection of digital identities based on multiple underlying technologies, implementations, and providers. Using this approach, customers can continue to use their existing identity infrastructure investments, choose the identity technology that works best for them, and more easily migrate from old technologies to new technologies without sacrificing interoperability with others. The Identity Metasystem is based upon the principles in The Laws of Identity.

Overview

There are three participants in digital identity interactions using Information Cards:

  • Identity Providers issue digital identities for you. For example, businesses might issue identities to their customers, governments might vouch for the identities of their citizens, credit card issuers might provide identities enabling payment, online services could provide verified data such as age, and individuals might use self-issued identities to log onto web sites.
  • Relying Parties accept identities for you. Online services that you use can accept digital identities that you choose and use the information provided by them on your behalf, with your consent.
  • Subject is yourself, the party in control of all these interactions. The subject can choose which of its applicable digital identities to use with the relying party.

Selectors

Microsoft's Windows CardSpace implementation of an Identity Selector

An Identity Selector is used to store, manage, and use their digital identities. Examples of Identity Selectors are Microsoft's Windows CardSpace, the Bandit Project's DigitalMe, and several kinds of Identity Selectors from the Eclipse Higgins Project.

An Identity Selector performs the following user-centric identity management tasks:

  • Provides a consistent user experience for authentication (and in some cases other kinds of interactions) with a Relying Party (also known as a Service Provider).
  • Provides a user interface that displays a set of Information Card icons from which the user selects their preferred Information Card when authentication is required by a local application or Relying Party (e.g. a web site's login page).
  • Provides a user interface to create and manage personal (also known as self-issued) Information Cards.
  • Provides a local Security Token Service that is used to issue the security tokens for personal Information Cards.
  • Provides a user interface to import and export Information Cards in standard file formats.
  • Is invoked by a browser extension or by a local rich client application.

An Identity Selector may also allow the user to manage (e.g. create, review, update, and delete cards within) their portfolio of Information Cards.

Components of the Identity Metasystem

There are five key components to the Identity Metasystem:

  • A way to represent identities using claims. Claims are carried in security tokens, as per WS-Security.
  • A means for identity providers, relying parties, and subjects to negotiate. Dynamically negotiating the claims to be delivered and the security token format used enables the Identity Metasystem to carry any format of token and any kinds of claims needed for a digital identity interaction. Negotiation occurs using WS-SecurityPolicy statements exchanged using WS-MetadataExchange.
  • An encapsulating protocol to obtain claims and requirements. The WS-Trust and WS-Federation protocols are used to carry requests for security tokens and responses containing those tokens.
  • A means to bridge technology and organizational boundaries using claims transformation. Security Token Services (STSs) as defined in WS-Trust are used to transform claim contents and formats.
  • A consistent user experience across multiple contexts, technologies, and operators. This is achieved via Identity Selector client software such as Windows CardSpace representing digital identities owned by users as visual Information Cards.

Generic qualities

  • I-cards are created by an entity known as a issuer.
  • I-cards display the name of the issuer (issuerName) in a text string.
  • I-cards have a text string to identify the card (cardName) that is initially set by the card issuer. Typically this card name is user-editable.
  • I-cards may have a (GIF or JPEG) background image (cardImage) set by the card issuer (user-editable).
  • In most i-cards the user is able to see the value of the claims.

Sign-In with Information Cards

The graphic used to indicate Information Card support

Using Information Cards, users can authenticate without needing a username and password for every web site; instead, at sites accepting them, they can log in with an Information Card, which may be used at multiple sites.

Each Information Card utilizes a distinct pair-wise digital key for every realm where a key is requested. A realm may be a single site or a set of related sites all sharing the same target scope information when requesting an Information Card. The use of distinct pair-wise keys per realm means that even if a person is tricked into logging into an imposter site with an Information Card, a different key would be used at that site than the site that the imposter was trying to impersonate; no shared secret is released.

Furthermore, many Identity Selectors provide a means of Phishing detection, where the HTTPS certificate of the Relying Party site is checked and compared against a list of the sites at which the user has previously used an Information Card. When a new site is visited, the user is informed that they have not previously used a card there.

Types of Information Card

The Identity Selector Interoperability Profile v 1.5 (or OASIS IMI v1.0 Committee Draft) specifies two types of Information Cards an Identity Selector must support.

  • Personal (also called Self-Issued) Information Cards: These cards allow you to issue Claims about yourself to sites willing to accept them. These claims can include your name, address, phone numbers, e-mail address, web address, birth date, gender, and a site-specific key uniquely generated for each site where the card is used.
  • Managed Information Cards: These cards allow Identity Providers other than yourself to make Claims about you to sites willing to accept them. These claims can include any information that a Relying Party requests, an Identity Provider is able to provide, and you are willing to send between them.

The Higgins project is defining two new kinds of Information Cards as well:

  • Relationship Cards (or R-cards) are used to establish an ongoing relationship between multiple parties.
  • Zero-Knowledge Cards (or Z-cards)

However the Information Card format allows for custom types; The Bandit project demonstrated prototype managed cards backed by OpenIDs at the BrainShare conference in March 2007.

Personal cards

The first kind of personal information cards were also introduced as part of Microsoft’s Windows CardSpace software in November 2006. Their behavior is also defined by the same documents covering the Microsoft-defined managed cards (see above).

Summary of characteristics:

  • Data format an XML file containing: set of claim type URIs as well as the (user-defined) values of these claims, cardImage, a unique cardID, etc. This data format is defined in the ISIP documents.
  • Issuer: The user's own identity selector. Personal cards can be described as self-issued
  • Genesis: Created by the user's identity selector.
  • Claims: 15 pre-defined claim types (e.g. firstname, surname, email address, etc.) are defined in the Identity Selector Interoperability Profile v 1.5 (or OASIS IMI v1.0 Committee Draft).
  • Authority: The user's identity selector is the authority for the issued token's set of claim values.
  • Data flow: On demand (e.g. as needed by a relying site), an STS local to the identity selector creates a security token with the current values.
  • Editability: The claim values are directly editable by the user.
  • Attribute data source: The personal card XML file contains claim values. When imported into an identity selector these data values are then managed internally by the selector.

Managed Information Card Details

The first kind of managed card was introduced as part of Microsoft’s Windows CardSpace software in November 2006. The behavior, file format and interoperability characteristics of these kinds of managed cards are defined by Microsoft documents such as the Identity Selector Interoperability Profile v 1.5 (or OASIS IMI v1.0 Committee Draft) (see here for a more complete list), in combination with open standards including WS-Trust and others.

Summary of characteristics:

  • Data format: an XML file containing: network endpoint of the STS, set of claim type URIs, name of the card, cardImage, issuerName, a unique cardID, etc. The XML file format is defined in the ISIP documents.
  • Issuer: An external, third party token service (representing an external person or organization).
  • Genesis: A managed card is generated by a Security Token Service running at an Identity Provider site and imported into the user's Identity Selector
  • Claims: The list of supported claim types (claim type URIs) is defined by the issuer.
  • Authority: The issuer is the sole authority for the claim values contained within the token it issues.
  • Data flow: Managed cards contain a network endpoint reference to a Security Token Service (STS) that, when requested by the identity selector (using WS-Trust, etc.) generates/provides a security token containing the required claims.
  • Editability: Underlying attribute data is not directly editable by the user.
  • Attribute data source: Determined by the issuer, and generally managed by the issuer.

Information Cards issued by third parties can employ any of four methods for the user to authenticate himself as the card owner:

  • a Personal (Self-Issued) Information Card,
  • an X.509 certificate (which can either be from a hardware device such as a SmartCard or it can be a software certificate),
  • a Kerberos ticket, such as those issued by many enterprise login solutions, or
  • a username and password for the card.

Additional methods could also be implemented by future Identity Selectors and Identity Providers (see #Futures).

Managed Information Cards can be auditing, non-auditing, or auditing-optional:

  • Auditing cards require the identity of the Relying Party site to be disclosed to the Identity Provider. This can be used to restrict which sites the Identity Provider is willing to release information to.
  • Non-auditing cards will not disclose the identity of the Relying Party site to the Identity Provider.
  • Auditing-optional cards will disclose the identity of the Relying Party site if provided by the Relying Party, but do not require this disclosure.

Relationship cards

Relationship cards are under development by the Higgins project (see http://wiki.eclipse.org/R-Card)

Summary of characteristics:

  • Data format: A managed card that supports a resource-udi claim
  • Supported Claims: Like all managed (or personal) cards, r-cards include a list of supported claim types (expressed as URIs) as defined by the issuer. This set defines the maximal set of claims that issuer will include in its generated security token. These claims are inherited from underlying ISIP-m-card upon which it is based and are used for the same purposes. Beyond managed cards the resource-udi "meta" claim provides a reference to a set of attributes.
  • Authority: The issuer is the authority for the issued token's set of claim values (as per a normal managed or personal card).
  • Editability: The values of underlying attributes (referenced by the resource-udi claim) may be editable by parties other than the issuer.
  • Supported Attributes: The value of an r-card's resource-udi claim is an Entity UDI (URI) that "points to" a data entity (representing a person, organization, or other object). The set of attributes of this data entity is distinct from (though usually a superset of) the "supported claims" mentioned above.

Reliance on the Higgins Data Model

Conceptually a managed card is essentially a human-friendly "pointer" to a Token Service—a web service (e.g. a WS-Trust Security Token Service) from which security tokens can be requested. A security token is a set of attribute assertions (aka claims) about some party that is cryptographically signed by the issuer (the token service acting as the authority). An r-card, contains a second "pointer" that points to a data entity whose attribute's values (i) shared by all parties to the r-card and (ii) form the underlying attributes that are consumed by the r-card issuer's STS and provide the values of the claims that this STS makes. By including this second "pointer" on the r-card, r-card holders have the potential to access and update some subset of these underlying attributes. The card issuer maintains an access control policy to control who has what level of access.

This second pointer is an Entity UDI—a reference to an Entity object in the Higgins Context Data Model. Entity UDIs may be dereferenced and the underlying Entity's attributes accessed by using the Higgins project's Identity Attribute Service.[1] Once resolved, consumers of this service can inspect, and potentially modify the attributes of the entity as well as get its schema as described in Web Ontology Language (OWL).

In addition to basic identity attribute values like strings and numbers, the data entity referred to by an r-card can have complex attribute values consisting of aggregates of basic attribute types as well as UDI links to other entities.

Claims

Beyond being used to log into sites, Information Cards can also facilitate other kinds of interactions. The Information Card model provides great flexibility because cards can be used to convey any information from an Identity Provider to a Relying Party that makes sense to both of them and that the person is willing to release. The data elements carried in Information Cards are called Claims.

One possible use of claims is online age verification, with Identity Providers providing proof-of-age cards, and Relying Parties accepting them for purposes such as online wine sales; other attributes could be verified as well. Another is online payment, where merchants could accept online payment cards from payment issuers, containing only the minimal information needed to facilitate payment. Role statements carried by claims can be used for access control decisions by Relying Parties.

Interoperability and licensing

The protocols needed to build Identity Metasystem components can be used by anyone for any purpose with no licensing cost and interoperable implementations can be built using only publicly available documentation. Patent promises have been issued by Microsoft, IBM, and others ensuring that the protocols underlying the Identity Metasystem can be freely used by all.

The Information Cards defined by the Identity Selector Interoperability Profile v 1.5 (or OASIS IMI v1.0 Committee Draft) are based on open, interoperable communication standards. Interoperable Information Card components have been built by dozens of companies and projects for platforms including Windows, Mac OS, and Linux, plus a prototype implementation for phones. Together, these components implement an interoperable Identity Metasystem. Information Cards can be used to provide identities both for Web sites and Web Services applications.

Several interoperability testing events for Information Cards have been sponsored by OSIS and the Burton Group, one was at the Interop at the October 2007 European Catalyst Conference in Barcelona and the most recent was at RSA 2008. These events are helping to ensure that the different Information Card software components being built by the numerous participants in the Identity Metasystem work well together.

The protocols needed to build Information Card implementations based on the Identity Selector Interoperability Profile v 1.5 (or OASIS IMI v1.0 Committee Draft) can be used by anyone for any purpose at no cost and interoperable implementations can be built using only publicly available documentation. Patent promises have been issued by Microsoft, IBM, and others, ensuring that this Information Card technology is freely available to all.

In June 2008, industry leaders including Equifax, Google, Microsoft, Novell, Oracle, PayPal and others created the Information Card Foundation in order to advance the use of the Information Card metaphor as a key component of an open, interoperable, royalty-free, user-centric identity layer spanning both the enterprise and the Internet.

In his report on the Interop at the June 2007 Catalyst Conference in San Francisco, analyst Bob Blakley wrote:

The interop event was a milestone in the maturation of user-centric identity technology. Prior to the event, there were some specifications, one commercial product, and a number of open-source projects. After the event, it can accurately be said that there is a running identity metasystem.

History of the terms "i-card" and "information card"

The term information card was introduced by Microsoft in May 2005 as a name for the visual information card metaphor to be introduced in its forthcoming Windows CardSpace software. Until early 2006, information cards were also sometimes referred to by the code-name “InfoCard”, which was not a name that was freely available for all to use. The name information card was specifically chosen as one that would be freely available for all to use, independent of any product or implementation. The name “information card” is not trademarked and is so generic as to not be trademarkable.

The term i-card was introduced at the June 21, 2006, Berkman/MIT Identity Mashup conference.[2][3] The intent was to define a term that was not associated with any industry TM or other IP or artifact. At the time, Microsoft had not yet finished applying the Open Specification Promise to the protocols underlying Windows CardSpace and there was also a misunderstanding that the term information card was not freely available for use by all, so to be conservative, the term i-card was introduced.

Mike Jones, of Microsoft, explained to participants of a session at IIW 2007b that Microsoft always intended the term information card to be used generically to describe all kinds of information cards and to be freely usable by all, and tried to correct the earlier misunderstanding that the term might apply only to the kinds of information cards originally defined by Microsoft. He made the case that the industry would be better served by having everyone use the common term information card, than having two terms in use with the same meaning, since there remains no legal or technical reason for different terms. In this case the term i-card would become just the short form of information card, just like e-mail has become the short form of electronic mail.

Software Implementations

See also

References

  1. ↑ [http://wiki.eclipse.org/Identity_Attribute_Service IdAS>
  2. ↑ MIT Identity Mashup conference meeting notes
  3. ↑ Drummond Reed's blog post

Additional resources

External links

This article is issued from Wikipedia. The text is available under the Creative Commons Attribution/Share Alike; additional terms may apply for the media files.