Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "I-Card Service 1.1"

(SCRPPSService)
(Data Model)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 
 
[[Image:Higgins_logo_76Wx100H.jpg|right]]
 
[[Image:Higgins_logo_76Wx100H.jpg|right]]
  
Line 20: Line 19:
  
 
== SCRPPSService  ==
 
== SCRPPSService  ==
The SOAP endpoint is defined here: [https://higgins.eclipse.org:3001/cardsync-new/services/SCRPPSService?WSDL SCRPPSService WSDL] .
+
The SOAP endpoint is defined here: [https://higgins.eclipse.org:3001/cardsync-new/services/SCRPPSServiceAIR?WSDL SCRPPSService WSDL] .
 
* The service assumes transport level security  
 
* The service assumes transport level security  
 
* Most messages are authenticated using an AccessToken.
 
* Most messages are authenticated using an AccessToken.
Line 40: Line 39:
  
 
== 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". This page describes an updated version of PDM called [[Persona Data Model 1.1]].
+
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 Persona Data Model 1.0.

Latest revision as of 15:14, 15 August 2014

Higgins logo 76Wx100H.jpg

The SOAP I-Card Service provides the core processing services for thin-client selectors including: AIR Selector 1.1-Win as well as for the Cloud Selector 1.1 and the iPhone Selector 1.1.

Versions

There are two variants of the I-Card Service: RPPSService and SCRPPSService. The I-Card Service 1.0 was introduced in Higgins 1.0 and supported the RPPSService variant. RPPSService is used by Higgins Embedded-Selector Extension for Firefox and the I-Card Manager.


In I-Card Service 1.1 the RPPSService has been replaced by the SCRPPSService service. The SCRPPSService is used by AIR Selector 1.1-Win, AIR Selector 1.1-Mac and the IPhone Selector.

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

SCRPPSService

The SOAP endpoint is defined here: SCRPPSService WSDL .

  • The service assumes transport level security
  • Most messages are authenticated using an AccessToken.

Implementation

Architecture

I-card-service-1.1.102.png

(Diagram Key)

Components & Packages

Components:

Packages:

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 Persona Data Model 1.0.

Back to the top