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.
Difference between revisions of "ISS Web UI"
(→Overview) |
(→Overview) |
||
| Line 4: | Line 4: | ||
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]]). | 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 | + | 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. [[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). | 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). | ||
Revision as of 11:16, 30 October 2006
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 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. 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).