|
|
| (12 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} This page describes the Higgins Personal Data Store. For an overview see [[Personal Data Store Overview]].
| |
| | | | |
| − | The PDS is comprised of a number of components shown in the diagram shown here [[Personal Data Store Overview]].
| |
| − |
| |
| − | === PDS Agent ===
| |
| − |
| |
| − | *An evolution of the Cloud Selector 1.1 from Higgins 1.1 with broader functionality.
| |
| − |
| |
| − | === PDS Vault ===
| |
| − |
| |
| − | The PDS vault is a variant of the [[IdAS Proxy Service]], with the following changes:
| |
| − |
| |
| − | *The [[Org.eclipse.higgins.idas.udi|UDI Resolver]] is configured to support '''sync://''' UDIs
| |
| − | *The [[Org.eclipse.higgins.idas.registry|IdAS Registry]] is configured to include the [[Org.eclipse.higgins.idas.cp.rdf2|RDF2]] [[Context Provider]].
| |
| − |
| |
| − | The [[IdAS Proxy Service]] is layered over the [[Attribute Service 1.1]] to provide 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.
| |
| − |
| |
| − | The PDS Vault can be accessed by:
| |
| − |
| |
| − | *Sending [[XDI]] messages to its endpoint
| |
| − | *Using the following low level client libraries:
| |
| − | **[[Org.eclipse.higgins.idas.client]] (Java IdAS Client)
| |
| − | **[[Org.eclipse.higgins.idasclient.cpp.core]] (C++ IdAS Client)
| |
| − | *Using the [[PDS Client 2.0]] mentioned below
| |
| − |
| |
| − | === PDS Client ===
| |
| − |
| |
| − | The [[PDS Client 2.0]] is a library used to access the [[Personal_Data_Store_2.0]].
| |
| − |
| |
| − | === Authentication (AuthN) Service ===
| |
| − |
| |
| − | The [[IdAS Proxy Service 2.0]] and [[Attribute Service 2.0]] 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.
| |
| − |
| |
| − | === Authorization Manager ===
| |
| − |
| |
| − | *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.
| |
