Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Higgins Selector

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

This page describes the Higgins Selector.

Higgins site card1.png

A card selector is a piece of software that runs on a computer or mobile device. The user can get cards from card issuing websites and can store them in this selector in much the same way a person puts business, library, loyalty and payment cards in their wallet.

  • By clicking on a card you can log into sites. No more passwords.
  • By clicking on a card you express yourself. No more filling in forms.
  • You can share cards with friends and businesses you trust.
  • Some cards create permanent connections to your friends, communities and businesses.
Selector-agentv6.png

Selector

Higgins Selector 1.0:

Higgins Selector 1.1 planned:

Selector-Supporting Services

Some selector clients take advantage of these web services:

Cloud Selector
The Cloud Selector 1.1 makes your cards available as OpenIDs. Reads card data from an I-Card Service, so no client software is required. (Higgins 1.1 only)
I-Card Service
Some selectors are designed as "thin clients" that only implement the user interface portion and rely on a hosted I-Card Service for core functionality. (Higgins 1.0 & 1.1).
I-Card Manager
Thin client selectors use the I-Card Manager Google GWT-based app to provide a web interface to view, update and manage your cards hosted on the I-Card Service. (Higgins 1.0 only)
CardSync Service
The CardSync Service makes sure that all of your cards are available across all of your computers and mobile devices. (Higgins 1.1)
Attribute Service
The Attribute Service 1.1 stores self asserted identity data and makes it available for data sharing with others. It also provides data gateway services to connect the client selector with a variety of back end data stores. (Higgins 1.1 only)
Authentication Service
For 1.1 we are working to make the CardSync Service and the Attribute Service rely on an external Authentication Service 1.1. Eventually the I-Card Service will also rely on it.(Higgins 1.1 only)

Back to the top