Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "PDS Architecture"

Line 4: Line 4:
  
 
==Higgins 1.1 web services (planned)==
 
==Higgins 1.1 web services (planned)==
;Personal Data Store: The [[Personal Data Store 1.1]] stores self asserted identity data and makes it available for data sharing with others. It also provides data gateway services to connect the client selector with a variety of back end data stores.  
+
===Personal Data Store===
;IdAS Proxy Service: Allows selectors using the C++ IdAS client library to access the Personal Data Store service.
+
A [[Personal Data Store 1.1]] is a combination of web services that stores personal (self-asserted) data, that makes it available to selector clients, and that provides user-managed authorization to permissioned third parties. It makes use of the following services:
;Authorization Manager: Gives the user control over the flows of data from a managed relationship card provider to a relying party. We plan to use/adapt Kantara UMA protocols.
+
* [[Attribute Service 1.1]] provides a bi-directional, synchronizing XDI endpoint over data managed by Context Provider plug-ins to the IdAS package. These context providers area also data adapters to a variety of back end data stores.  
;Cloud Selector: The [[Cloud Selector 1.1]] makes your cards available as OpenIDs. Reads card data from an I-Card Service, so no client software is required.
+
* [[IdAS Proxy Service 1.1]] allows selector clients using the C++ IdAS client library to access the Attribute service.
;CardSync Service: The [[CardSync Service]] makes sure that all of your cards are available across all of your computers and mobile devices.
+
* [[CardSync Service]] is a specialized bi-directional, synchronizing XML endpoint for synchronizing i-card data managed by the IdAS package.
;Authentication Service: For 1.1 we are working to make the [[CardSync Service]] and the [[Attribute Service]] rely on an external [[Authentication Service 1.1]]. Eventually the [[I-Card Service]] will also rely on it.
+
* Authorization Manager (planned) gives the user control over the flows of data from a managed relationship card provider to a relying party. We plan to use/adapt Kantara UMA protocols.
;I-Card Service: Some selectors are designed as "thin clients" that only implement the user interface portion and rely on a hosted [[I-Card Service]] for core functionality.
+
 
 +
===Cloud Selector ===
 +
* [[Cloud Selector 1.1]] makes i-cards available as OpenIDs. It reads card data from an I-Card Service, so no client software is required.  
 +
* [[I-Card Service 1.1]] provides core i-card management services for both the cloud selector as well as "thin client" (UI-only) selectors
 +
 
 +
===Authentication Service===
 +
;Authentication Service: For 1.1 we are working to make the [[CardSync Service]] and the [[Attribute Service 1.1]] rely on an external [[Authentication Service 1.1]]. Eventually the [[I-Card Service]] will also rely on it.
  
 
==Higgins 1.0 services==
 
==Higgins 1.0 services==

Revision as of 00:08, 10 November 2009

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins.funnell.PNG


Higgins 1.1 web services (planned)

Personal Data Store

A Personal Data Store 1.1 is a combination of web services that stores personal (self-asserted) data, that makes it available to selector clients, and that provides user-managed authorization to permissioned third parties. It makes use of the following services:

  • Attribute Service 1.1 provides a bi-directional, synchronizing XDI endpoint over data managed by Context Provider plug-ins to the IdAS package. These context providers area also data adapters to a variety of back end data stores.
  • IdAS Proxy Service 1.1 allows selector clients using the C++ IdAS client library to access the Attribute service.
  • CardSync Service is a specialized bi-directional, synchronizing XML endpoint for synchronizing i-card data managed by the IdAS package.
  • Authorization Manager (planned) gives the user control over the flows of data from a managed relationship card provider to a relying party. We plan to use/adapt Kantara UMA protocols.

Cloud Selector

  • Cloud Selector 1.1 makes i-cards available as OpenIDs. It reads card data from an I-Card Service, so no client software is required.
  • I-Card Service 1.1 provides core i-card management services for both the cloud selector as well as "thin client" (UI-only) selectors

Authentication Service

Authentication Service
For 1.1 we are working to make the CardSync Service and the Attribute Service 1.1 rely on an external Authentication Service 1.1. Eventually the I-Card Service will also rely on it.

Higgins 1.0 services

I-Card Manager
Thin client selectors use the I-Card Manager Google GWT-based app to provide a web interface to view, update and manage your cards hosted on the I-Card Service.
I-Card Service
Some selectors are designed as "thin clients" that only implement the user interface portion and rely on a hosted I-Card Service for core functionality.

Misc. Building Blocks

This section describes the data related services, java frameworks and data models that are used by the personal data agent services.

Data Models

IdAS Solution

The IdAS solution provides a testbed for exercising the IdAS Java framework.

XDI4J

XDI4J is a java library for working with XDI.

Back to the top