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.0 Package"
(→Architectural Discussions) |
|||
Line 1: | Line 1: | ||
− | The [[Identity Attribute Service]] (IdAS) component provides a virtualized, unified view and a common means of access to identity information from multiple heterogeneous data sources. IdAS is an extensible framework based on the [[Higgins Data Model]] that represents identities ([[ | + | The [[Identity Attribute Service]] (IdAS) component provides a virtualized, unified view and a common means of access to identity information from multiple heterogeneous data sources. IdAS is an extensible framework based on the [[Higgins Data Model]] that represents identities ([[Entity | Entities]]) and their [[Identity Attribute]]s in a [[Context]]. Data sources are adapted to the IdAS framework via plug-ins called [[Context Provider]]s. |
The IdAS framework is comprised of three sub-components (see [http://wiki.eclipse.org/index.php/Components#Identity_Attribute_Service_and_Context_Providers Components page] for more details): | The IdAS framework is comprised of three sub-components (see [http://wiki.eclipse.org/index.php/Components#Identity_Attribute_Service_and_Context_Providers Components page] for more details): | ||
− | ; [[IdAS API]]: Allows a consumer to perform access and update operations (as allowed) on elements of the [[Higgins Data Model]]. Specifically, the consumer can obtain an object which represents a [[Context]], can read and change [[ | + | ; [[IdAS API]]: Allows a consumer to perform access and update operations (as allowed) on elements of the [[Higgins Data Model]]. Specifically, the consumer can obtain an object which represents a [[Context]], can read and change [[Entity | Entities]] within that [[Context]], and can read and change [[Identity Attribute | attributes]] on those subjects. |
; [[IdAS SPI]]: Is used by parties who wish to write [[Context Provider]]s 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. | ; [[IdAS SPI]]: Is used by parties who wish to write [[Context Provider]]s 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. | ||
− | ; [[IdAS Registry]]: Is responsible for resolving a [[ | + | ; [[IdAS Registry]]: Is responsible for resolving a [[ContextIdDatatype]] 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. |
; [[IdAS Common]]: A set of common, useful utility methods. | ; [[IdAS Common]]: A set of common, useful utility methods. | ||
Revision as of 00:37, 1 February 2008
The Identity Attribute Service (IdAS) component provides a virtualized, unified view and a common means of access to identity information from multiple heterogeneous data sources. IdAS is an extensible framework based on the Higgins Data Model that represents identities ( Entities) and their Identity Attributes in a Context. Data sources are adapted to the IdAS framework via plug-ins called Context Providers.
The IdAS framework is comprised of three sub-components (see Components page for more details):
- IdAS API
- Allows a consumer to perform access and update operations (as allowed) on elements of the Higgins Data Model. Specifically, the consumer can obtain an object which represents a Context, can read and change Entities within that Context, and can read and change attributes on those subjects.
- 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.
- IdAS Registry
- Is responsible for resolving a ContextIdDatatype 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.
- IdAS Common
- A set of common, useful utility methods.
Plan
This section relates to the union of the IdAS API, SPI, Common and Registry sub-components.
Architectural Discussions
- IdAS Change Password
- IdAS And IGF
- IdAS API Extensibility
- Data Model Open Issues
- Access Control in IdAS
Service
- See IdAS API
- See also IdAS SPI, IdAS Common, IdAS Registry
Use cases
See Also
- IdAS API
- IdAS SPI
- IdAS Common
- IdAS Registry
- Context Provider --definition of the term
- Components page --overview of the IdAS Component and a list of available Context Providers