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 "I-Card Service 1.0"
(New page: {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} right The SOAP I-Card_Service provides the core processing services for thin-clien...) |
|||
| Line 23: | Line 23: | ||
''([[Diagram Key]])'' | ''([[Diagram Key]])'' | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Data Model == | == Data Model == | ||
Within the [[I-Card_Service]]'s [[RPPS Package]] are some components that persist data objects on behalf of the user. These include user account data, the users set of cards, and other data. Some components use IdAS to persist their data. Others manage their own local data stores "above" IdAS. We call this data model "Personal Data Model 1.0". | Within the [[I-Card_Service]]'s [[RPPS Package]] are some components that persist data objects on behalf of the user. These include user account data, the users set of cards, and other data. Some components use IdAS to persist their data. Others manage their own local data stores "above" IdAS. We call this data model "Personal Data Model 1.0". | ||
Revision as of 23:37, 21 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
The SOAP I-Card_Service provides the core processing services for thin-client selectors including: Higgins Embedded-Selector Extension for Firefox as well as the I-Card Manager.
Versions
The I-Card_Service was introduced in Higgins 1.0 and supports the RPPSService endpoint.
RPPSService
The SOAP endpoint is defined here: RPPSService WSDL.
- The service assumes transport level security
- Most messages include a username and password for authentication
- Approximately 110 message types
Implementation
Architecture
Data Model
Within the I-Card_Service's RPPS Package are some components that persist data objects on behalf of the user. These include user account data, the users set of cards, and other data. Some components use IdAS to persist their data. Others manage their own local data stores "above" IdAS. We call this data model "Personal Data Model 1.0".