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.
Difference between revisions of "IdAS Solution 1.0"
(→Background) |
m (logo, category, left menu) |
||
| Line 1: | Line 1: | ||
| + | {{#eclipseproject:technology.higgins}} | ||
| + | [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
== Overview == | == Overview == | ||
The [[Identity Attribute Service]] and supporting [[Context Provider]]s are typically deployed part of a larger solution, but it may be useful in its own right. | The [[Identity Attribute Service]] and supporting [[Context Provider]]s are typically deployed part of a larger solution, but it may be useful in its own right. | ||
| Line 23: | Line 25: | ||
* [[Solutions]] | * [[Solutions]] | ||
| − | + | [[Category:Higgins Solutions]] | |
| − | + | ||
Revision as of 15:07, 18 March 2008
{{#eclipseproject:technology.higgins}}
Overview
The Identity Attribute Service and supporting Context Providers are typically deployed part of a larger solution, but it may be useful in its own right.
On this page we plan to document a number of sample IdAS-only solutions ranging from a very simple example to more sophisticated examples which illustrate identity federation, mapping, and virtualization.
Intro to IdAS
The Identity Attribute Service (IdAS) provides a Java API that exposes read/write-able data from a wide variety of external data sources that can be "plugged in" to the Higgins Global Graph. (Note that the IdAS API implements but does not define the semantics of the Higgins Global Graph model.)
Context Provider plug-ins to IdAS are used to adapt external systems, sites, databases, or other data sources to the IdAS API. These Context Providers are responsible for data transformation between the Higgins model and their own internal data model. Higgins does not constrain the Context Provider's choice of data representation; it can be XML-based, object-oriented, relational, or anything else.
Context Providers can be used to adapt data stores/sources such as:
- Directories: LDAP stores like eDirectory, Active Directory, OpenLDAP, etc.
- Relational databases: used by enterprise apps to store identity/profile information.
- Online social networks (node-edge graphs): data behind Facebook, MySpace, LinkedIn, etc.
- Messaging systems: email, IM, collaboration client contact/buddy lists.
- Website account "silos": personal profile and preference information stored sites like eBay, Amazon, Google Groups, Yahoo Groups, etc.
Basic Standalone
This simple solution combines IdAS, the JNDI Context Provider, and an LDAP server to provide an identity store which is then accessed by an application.