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.
Difference between revisions of "IdAS 1.1 Package"
(→Architecture) |
(→Data Models) |
||
Line 26: | Line 26: | ||
=== Data Models === | === Data Models === | ||
− | As mentioned above, the [[IdAS_1.1_Package]] implements the general purpose [[ | + | As mentioned above, the [[IdAS_1.1_Package]] implements the general purpose [[Higgins Data Model 1.1]] that can be used for many different applications. You can think of the Higgins [[I-Card Service]] and [[CardSync Service]] as "applications" built on the common [[RPPS Package]]. This RPPS package implements a narrower data model that is an "application" of [[Higgins Data Model 1.1]]. We call this the [[Persona Data Model 1.1]]: |
[[Image:Data-models-1.1.101.png|center]] | [[Image:Data-models-1.1.101.png|center]] |
Revision as of 08:53, 24 January 2010
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}} The IdAS 1.1 Package (IdAS) is a package of components that provides a virtualized, unified view and a common means of access to identity information from multiple heterogeneous data sources. IdAS is an extensible framework that implements the Context Data Model 1.1 (CDM). CDM represents objects (called Entities) and their Attributes. Existing external data sources (e.g. databases, directories, etc.) are adapted to (mapped to and from) the IdAS via plug-ins called Context Providers.Architecture
Errata: the above diagram only shows some of the components listed below. It needs to be updated.
Components
The IdAS framework is comprised of these constituent projects (see this section) of the Components page for more details):
- Components 1.X#IdAS / Org.eclipse.higgins.idas.api
- Allows a consumer to perform access and update operations (as allowed) on elements of the Context Data Model. Specifically, the consumer can obtain an object which represents a Context, can read and change objects within that Context, and can read and change attributes on those subjects.
- Components 1.X#IdAS / Org.eclipse.higgins.idas.spi
- Is used by parties who wish to write Context Providers for IdAS. The IdAS API is only a set of interfaces which must be implemented by Context Providers. A Context Provider consists of the implementations of IdAS SPI interfaces which allow a consumer to access some specific type of identity store. One good way to see what is involved in building an IdAS Context Provider is to look at some of the existing Context Provider projects. It's suggested that the Org.eclipse.higgins.idas.cp.inmem project would be a good jumping-in point, as it tends to be fairly simple.
- Components 1.X#IdAS / Org.eclipse.higgins.idas.registry
- Is responsible for resolving an object identifier to all the information needed to obtain a suitable Context Provider, and to further instantiate the Context identified by the ContextId. IdAS Registry can keep an internal list of Context Providers and ContextIds, or it can use external mechanisms such as XRI Resolution.
- Components 1.X#IdAS / Org.eclipse.higgins.idas.common
- A set of common, useful utility methods and Authentication Materials classes.
- Components 1.X#IdAS / Org.eclipse.higgins.idas.udi
- Code for supporting the resolution of Context-, Entity- and Attribute UDIs.
Data Models
As mentioned above, the IdAS_1.1_Package implements the general purpose Higgins Data Model 1.1 that can be used for many different applications. You can think of the Higgins I-Card Service and CardSync Service as "applications" built on the common RPPS Package. This RPPS package implements a narrower data model that is an "application" of Higgins Data Model 1.1. We call this the Persona Data Model 1.1:
Use cases
See Also
- IdAS Authentication Materials
- Context Provider - definition of the term
- IdAS section of Components page --overview of the IdAS Component and a list of available Context Providers