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"
(→See Also) |
(→Services) |
||
| Line 12: | Line 12: | ||
# Verification of HBX authentication | # Verification of HBX authentication | ||
# Returns the Terms of Service text on request | # Returns the Terms of Service text on request | ||
| − | # | + | # HTML form filling - If [[RP Protocol Support]] has a form filling script for the current page&site, it can retreive data from the appropriate I-Card, and pass this data along with the script to HBX so that HBX can fill in forms on that page |
| − | # | + | # HBML scraping - If [[RP Protocol Support]] has an HTML scraping script for the current page&site, pass this script to HBX and retreive from HBX attribute data that it can store in a site-specific IdASCard I-Card |
| − | # RSS | + | # RSS support - [[RP Protocol Support]] can create an RSS-SSE feed that publishes the minimal subset of attributes required/supported by the RP site from the appropriate I-Card. It can also subscribe to a reverse RSS-SSE feed and use the data to update the a site-specific IdASCard I-Card |
==See Also== | ==See Also== | ||
Revision as of 22:51, 15 November 2006
Overview
When the user's browser with the Higgins extension lands on a site that requires a Digital Identity for authentication, HBX sends a 'getDigitalIdentity' request RP Protocol Support. RP Protocol Support requests an I-Card handle from 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 RP Protocol Support will 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 RP Protocol Support to set up a channel between the site and an i-card (especially its associated IdAS Context). RP Protocol 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
- HTML form filling - If RP Protocol Support has a form filling script for the current page&site, it can retreive data from the appropriate I-Card, and pass this data along with the script to HBX so that HBX can fill in forms on that page
- HBML scraping - If RP Protocol Support has an HTML scraping script for the current page&site, pass this script to HBX and retreive from HBX attribute data that it can store in a site-specific IdASCard I-Card
- RSS support - RP Protocol Support can create an RSS-SSE feed that publishes the minimal subset of attributes required/supported by the RP site from the appropriate I-Card. It can also subscribe to a reverse RSS-SSE feed and use the data to update the a site-specific IdASCard I-Card