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

ISS Web UI

Revision as of 16:56, 28 October 2006 by Paul.socialphysics.org (Talk | contribs) (See Also)

Overview

The ISS Web UI is invoked by a Higgins client such as a web service, an enterprise client app or the Higgins Browser Extension. This client is operating on behalf of some relying party.

The ISS Web UI receives the relying party's policy. This policy describes the forms of digital information that it desires/requires, the protocols that it supports and the set of claims it requires. It first invokes the I-Card Selector Service to find a set of zero or more cards that match. (See I-Card Selector Service).

If there are more than one cards that satisfy the policy, then the ISS Web UI displays a visual "I-Card Selector" UI that shows all of the user's cards. Cards that don't satisfy the policy are greyed out. If the user clicks on one of the non-greyed-out cards, then they have thereby indicated that they approve the release of identity information that is implied. ISS Web UI examines the policy to determine whether a token or a URL, etc. is required, the kinds of tokens, information schemas, etc. are required, and so on. It then queries the appropriate method (e.g. TokenIssuerCard.requestDigitalIdentity() for a token or URLIssuerCard.getURL() for a URL, etc. and obtains the desired information. Its final step is to convey this information to the Higgins client.

If no cards satisfy the policy, but the policy accepts self-issued cards, then the ISS Web UI will present a user experience that allows the user to create a new card (presumably containing the required claims).

In deployments where the Higgins Browser Extension uses a remote ISS service, this webapp provides the I-Card Selector UI web pages that are displayed in the browser and allow the user to select a matching i-card from among those that match the relying party's policy, approve the release of its associated Digital Identity, and allow the user to create their own self-asserted i-cards.

See Also

Back to the top