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"
(→Overview) |
(→Overview) |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
| − | The [[Identity Attribute Service]] and supporting [[Context Provider]]s are typically deployed | + | 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. |
| + | |||
| + | 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. | ||
== Basic Standalone == | == Basic Standalone == | ||
Revision as of 19:20, 17 February 2008
Contents
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.
Basic Standalone
This simple deployment combines IdAS, the JNDI Context Provider, and an LDAP server to provide an identity store which is then accessed by an application.