Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "ISS Web UI"

(See Also)
m (Added tag for left menu)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{#eclipseproject:technology.higgins}}
 
==Overview==
 
==Overview==
The [[ISS Web UI]]'s main method getCard(RP_Policy) is invoked by [[RP Protocol Support]] and returns a matching I-Card handle.  
+
[[ISS Web UI]] is the name for the I-Card selector user interface running within HBX.
  
The [[ISS Web UI]] receives the relying party's ''policy'' (RP_Policy). This policy describes the forms of digital information that it desires/requires, the token or data stream formats 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]]).  
+
[[ISS Web UI]] displays the list of all of the users cards (greying out the ones that are not applicable for the current RP site). The intent is to "create a user interface which shares the same card metaphor, sequences of experiences and decision points (the ceremony) of CardSpace so that the user experience is as similar as possible across platforms." (as quoted from [[Response to Open Specification Promise]]).
  
If there is more than one card that satisfies 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. The selected card is returned to [[RP Protocol Support]]
+
==Links==
 
+
[[RP Protocol Support]], knowing the protocol to be used in interacting with the RP, determines whether a token or an RSS feed, etc. is required, the kinds of tokens, information schemas, etc. that are required, and so on. It then queries the appropriate method (e.g. TokenIssuerCard.requestDigitalIdentity() for a TokenIssuerCard or the IdAS methods for an IdASCard) and obtains the desired information. Its final step is to convey this information to the Higgins client using the appropriate protocol (e.g. HTTP POST of a token, URL, etc.)
+
 
+
If no cards satisfy the policy, but the policy accepts self-issued cards, then the [[I-Card Manager]] will be invoked to allow the user to create a new card (presumably containing the required claims).
+
 
+
==See Also==
+
 
* [http://eclipse.org/higgins Higgins Home]
 
* [http://eclipse.org/higgins Higgins Home]
* [[Architecture]]
 
* [[components]]
 
* [[I-Card Selector Service]]
 
* [[ISS Client UI]]
 

Latest revision as of 08:32, 15 March 2008

{{#eclipseproject:technology.higgins}}

Overview

ISS Web UI is the name for the I-Card selector user interface running within HBX.

ISS Web UI displays the list of all of the users cards (greying out the ones that are not applicable for the current RP site). The intent is to "create a user interface which shares the same card metaphor, sequences of experiences and decision points (the ceremony) of CardSpace so that the user experience is as similar as possible across platforms." (as quoted from Response to Open Specification Promise).

Links

Back to the top