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.
Difference between revisions of "Org.eclipse.higgins.rpps"
(→Overview) |
(→Overview) |
||
| Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
| − | When the user's browser with the Higgins extension lands on a site that requires a Digtial Identity for authorization, HBX | + | When the user's browser with the Higgins extension lands on a site that requires a Digtial Identity for authorization, HBX sends a 'getDigitalIdentity' request to [[ISS Web UI]] (that in turn passes this request through to the [[I-Card Selector Service]]). HBX will redirect the browser to the "card picker" page served up by [[ISS Web UI]] in order for the user to select the i-card from which to retreive the required Digital Identity. [Note: the card picker page only actually appears if the user has not previously approved the release and indicated in in the UI not to bother them again]. |
| − | Whether or not a site performs authentication as described, a site might support one or more protocols for | + | Whether or not a site performs authentication request/response exchange as described, a site might support one or more protocols for other kinds of identity data exchange that are not strictly about authentication. If so, HBX will again redirect to an [[ISS Web UI]]-driven page showing a set of one or more i-cards that represent these non-auth kinds of data exchange. |
| − | After this non-auth i-card has been selected, HBX uses the services of [[HBX Support]] to set up a channel between the site and an i-card (especially its associated IdAS Context). [[HBX Support]] is also responsible for managing the relationship between the user, the HBX "client" and the Higgins server. | + | After this (non-auth) i-card has been selected, HBX uses the services of [[HBX Support]] to set up a channel between the site and an i-card (especially its associated IdAS Context). [[HBX Support]] is also responsible for managing the relationship between the user, the HBX "client" and the Higgins server. |
===Services=== | ===Services=== | ||
Revision as of 14:56, 17 October 2006
Overview
When the user's browser with the Higgins extension lands on a site that requires a Digtial Identity for authorization, HBX sends a 'getDigitalIdentity' request to ISS Web UI (that in turn passes this request through to the I-Card Selector Service). HBX will redirect the browser to the "card picker" page served up by ISS Web UI in order for the user to select the i-card from which to retreive the required Digital Identity. [Note: the card picker page only actually appears if the user has not previously approved the release and indicated in in the UI not to bother them again].
Whether or not a site performs authentication request/response exchange as described, a site might support one or more protocols for other kinds of identity data exchange that are not strictly about authentication. If so, HBX will again redirect to an ISS Web UI-driven page showing a set of one or more i-cards that represent these non-auth kinds of data exchange.
After this (non-auth) i-card has been selected, HBX uses the services of HBX Support to set up a channel between the site and an i-card (especially its associated IdAS Context). HBX Support is also responsible for managing the relationship between the user, the HBX "client" and the Higgins server.
Services
Here are a list of the services that are provided to HBX:
- New account creation
- Verification of HBX authentication
- Returns the Terms of Service text on request
- Form fill support - provides HBX with data from the selected i-card (e.g. a screen scrape and form fill kind of i-card) which HBX to auto-fill web forms on external websites
- Screen scrape support - provides HBX with scripts from the selected i-card (e.g. a screen scrape and form fill kind of i-card) which HBX uses to scrape attribute data from remote sites
- RSS-P support - by interacting with an RSS-P i-card (as implmented by an RSS-P I-Card Provider) it retreives the URL of the RSS feed from the i-card's associated Context and delivers this URL to HBX so that it can post it to the relying site