keepcalculator

06 Numbers and Powers

Information Card Identity Selector Explained

Card No. 06·82505 · Updated · Standard formula, shown below

An information card identity selector is a software component that lets you choose which digital identity to present to a website or online service. You enter your credentials once into a local identity store, and the selector presents you with a visual list of your information cards—each representing a different identity or set of claims—so you can pick the one the relying party will accept. The selector then sends only the required claims to the site, without revealing your password or other unnecessary data.

Background: Where Did Information Cards Come From?

Information cards emerged in the mid-2000s as part of the broader “identity metasystem” vision, most notably championed by Microsoft’s CardSpace and the open-source Higgins project. The idea was to create a user-centric identity layer on top of the web, where users control which attributes (like name, email, or age) they share with each site. The selector was the user-facing piece of this system—the part that let you see and choose your identities.

The concept drew on earlier work like the Liberty Alliance and Shibboleth, but information cards were unique in that they put the user at the center. Instead of a site asking for a username and password, it would ask for a specific card, and the selector would let you pick one that meets the request. The technology never achieved widespread adoption, but its principles influenced later developments like OpenID Connect and FIDO2.

How an Identity Selector Works

At its core, an identity selector performs four steps:

  1. Discovery: The relying party (the website) sends a request for certain claims (e.g., “email address” and “age over 18”).
  2. Selection: The selector shows you a list of cards that can satisfy those claims. You pick one.
  3. Authentication: You prove you own that card, typically by entering a PIN, password, or using a biometric.
  4. Release: The selector sends only the required claims to the site, often via a signed token, without exposing your credentials.

Importantly, the selector never stores your credentials on the website’s server. It also doesn’t send the entire card—just the specific claims requested. This minimizes data exposure and reduces the risk of identity theft.

How to Choose an Identity Selector

If you were implementing a system that uses information cards, you’d need to choose a selector that fits your environment. Key factors include:

  • Platform support: Does it run on Windows, macOS, Linux, or mobile? CardSpace was Windows-only, which limited its reach.
  • Protocol compatibility: Does it support WS-Trust, SAML, or OpenID Connect? Different selectors speak different protocols.
  • Card storage: Where are the cards stored? Locally on disk, in a hardware token, or in a cloud vault?
  • User experience: How easy is it to manage multiple cards? Does it support drag-and-drop, search, or grouping?
  • Security features: Does it support biometric authentication, tamper-resistant storage, or audit logs?

In practice, most modern systems have moved away from standalone selectors and instead integrate identity selection into the browser or operating system. For example, Windows Hello and macOS Touch ID act as selectors for local identities, while services like “Sign in with Google” present a similar choice on the web.

Common Problems and Misconceptions

One common misconception is that an identity selector is the same as a password manager. They are different: a password manager stores credentials and auto-fills them, while a selector manages digital identities and releases claims. A selector might also store passwords, but its primary function is to choose which identity to present, not just to fill in a form.

Another issue is the “phishing problem.” Early selectors were designed to prevent phishing by making it impossible for a fake website to ask for a card—the selector would only respond to requests from legitimate relying parties. However, if a user was tricked into installing a malicious card, the protection failed. This led to the downfall of some implementations.

Technical problems also plagued the technology: interoperability between different vendors’ selectors was poor, and the WS-Trust protocol was complex. Many users found the concept of multiple cards confusing, preferring the simplicity of a single sign-on.

Comparisons: Information Cards vs. Modern Alternatives

Information cards were an early attempt at user-centric identity, but they lost out to other approaches:

  • OAuth and OpenID Connect: These protocols let users authorize a website to access their data from another service (like Google or Facebook). They are simpler and more widely adopted, but they often require trusting the identity provider to know what you’re doing.
  • FIDO2/WebAuthn: This uses public-key cryptography to authenticate without passwords. It’s more secure than cards but doesn’t handle the “which identity” question—you usually have one identity per device.
  • Self-sovereign identity (SSI): This newer concept gives users complete control over their identity data, often using blockchain. It’s conceptually similar to information cards but with more modern technology.

In many ways, information cards were ahead of their time. They anticipated the need for granular consent and data minimization, which are now central to privacy regulations like GDPR.

Safety and Privacy Considerations

When using any identity selector, you should consider:

  • Data minimization: Only share the minimum claims required. A good selector will let you see exactly what’s being requested.
  • Revocation: If a card is compromised, you need a way to revoke it. Make sure your selector supports this.
  • Local storage: Cards stored on your device should be encrypted. If you use a cloud-based selector, ensure the provider uses strong encryption and has a clear privacy policy.
  • Phishing resistance: Always verify that the website requesting a card is legitimate. A selector should only present cards to sites that are properly authenticated.

In practice, you’re unlikely to encounter a standalone information card selector today. But the principles it embodied—user control, data minimization, and phishing resistance—are more relevant than ever. Understanding how it worked helps you evaluate modern identity systems and make informed choices about your digital identity.

Frequently Asked Questions

Is an information card the same as a digital ID card?
No. A digital ID card is a specific credential, like a driver’s license or passport, that you might store on your phone. An information card is a broader concept—it represents a set of claims about you that you can present to a website. A digital ID card could be one type of information card, but information cards can also contain non-official data like your email address or age.

Why did Microsoft CardSpace fail?
CardSpace was technically sound but suffered from lack of adoption by websites and other identity providers. It required significant changes to web servers, and the user experience was confusing for many. Additionally, the rise of simpler OAuth-based solutions made it obsolete.

Can I still use information cards today?
Standalone information card selectors are largely defunct. However, the concept lives on in modern identity systems. For example, when you choose “Sign in with Apple” and it asks if you want to share your email, that’s a form of claim selection. Similarly, some government eID systems use a card-based metaphor.

What is a “claim” in this context?
A claim is a single piece of information about you, such as “name,” “email,” or “age over 18.” An information card contains one or more claims. When you use a selector, you can choose which claims to release to a website, rather than giving it all your data.

Is an identity selector the same as a single sign-on (SSO) tool?
No, though they serve similar purposes. SSO tools like Okta or Azure AD let you log in once and access many sites without re-entering credentials. An identity selector is more granular—it lets you choose which identity to use for each site, and it can release different claims to different sites. SSO typically uses one identity for all sites.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →