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

PDS Architecture

Revision as of 11:32, 30 March 2010 by Unnamed Poltroon (Talk) (Higgins 2.0)

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

Higgins.funnell.PNG

Higgins 1.0 and 1.1 services

Web 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 1.1 for core functionality.
CardSync Service 1.1
A specialized bi-directional, synchronizing XML endpoint for synchronizing i-card data stored on a co-resident I-Card Service 1.1

Web Apps

Cloud Selector 1.1
Makes i-cards available as OpenIDs. It reads card data from the I-Card Service, so no client software is required.

Higgins 2.0

Under development for Higgins 2.0

Higgins pds (2).png

Web Portal

  • We plan to develop a Web Portal--an evolution of the Cloud Selector 1.1 from Higgins 1.1 with broader functionality.

Personal Data Store (web service)

A Personal Data Store 2.0 is a combination of web services that stores personal (self-asserted) data, that makes it available to active clients, and that provides user-managed authorization of sharing to third parties. It is comprised 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.

Authorization Manager (web service)

  • 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.

Authentication Service (web service)

The IdAS Proxy Service 1.1 and Attribute Service 1.1 require access tokens minted by the Authentication Service 2.0. Eventually the I-Card Service and CardSync Service will also rely on this external authN service.

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 is a testbed for exercising the IdAS Java framework.

XDI4J

XDI4J is a java library for working with XDI.

Back to the top