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"
(New page: == Architecture == Image:deploy-idas-v43.JPG == See Also == * Deployments == Links == * [http://eclipse.org/higgins Higgins Home]) |
(→Basic Standalone) |
||
| (22 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} | |
| − | [[Image: | + | [[Image:Higgins_logo_76Wx100H.jpg|right]] |
| − | + | The Identity Attribute Service (IdAS) is a pluggable framework for the integration and abstraction of identity and relationship data across multiple data sources. IdAS uses the Higgins [[Context Data Model]] (CDM), which provides a foundation for integrating, unifying, and sharing identity-related data. | |
| − | + | ||
| − | == | + | 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 [[Context Data Model]] (CDM). IdAS is extended by [[Context Provider]] plug-ins that adapt data from external systems, sites, databases and make them available via the IdAS API. These [[Context Provider]]s 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 Provider]]s 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 == | ||
| + | The [[Identity Attribute Service 1.0]] and supporting [[Context Provider]] plugins are typically deployed part of a larger solution, but is useful in its own right. For example... | ||
| + | |||
| + | This [[IdAS Basic Deployment | simple solution]] combines IdAS, the JNDI Context Provider, and an LDAP server to provide an identity store which is then accessed by an application. | ||
| + | |||
| + | [[Category:Higgins Solutions]] | ||
| + | [[Category:Higgins IdAS]] | ||
Latest revision as of 23:45, 16 March 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
The Identity Attribute Service (IdAS) is a pluggable framework for the integration and abstraction of identity and relationship data across multiple data sources. IdAS uses the Higgins Context Data Model (CDM), which provides a foundation for integrating, unifying, and sharing identity-related data.
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 Context Data Model (CDM). IdAS is extended by Context Provider plug-ins that adapt data from external systems, sites, databases and make them available via 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
The Identity Attribute Service 1.0 and supporting Context Provider plugins are typically deployed part of a larger solution, but is useful in its own right. For example...
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.