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 "Architecture"
(→See Also) |
|||
Line 23: | Line 23: | ||
* Local Apps (e.g. Eclipse RCP apps and other enterprise apps) can invoke a local instance of [[RP Protocol Support]] that uses a locally running [[ISS Client UI]] (card selector UI). | * Local Apps (e.g. Eclipse RCP apps and other enterprise apps) can invoke a local instance of [[RP Protocol Support]] that uses a locally running [[ISS Client UI]] (card selector UI). | ||
− | == | + | ==Links== |
* [http://eclipse.org/higgins Higgins Home] | * [http://eclipse.org/higgins Higgins Home] | ||
** [http://wiki.eclipse.org/index.php/Higgins_Wiki Wiki] | ** [http://wiki.eclipse.org/index.php/Higgins_Wiki Wiki] |
Revision as of 11:42, 12 April 2007
Core Components Changes --changes to the above diagram
Components
- Higgins Browser Extension
- RP Enablement
- I-Card Manager
- RP Protocol Support
- ISS Client UI
- I-Card Selector Service (ISS)
- I-Card Registry
- I-Card Provider
- Token Service
- Token Provider
- Identity Attribute Service (IdAS)
- Context Provider
Clients/Consumers
Client apps and services that use these core components are expected to include:
- Relying Party (Service Provider)s can use the "RP Enablement" component to add support (e.g. to validate tokens) for identity protoocols
- Local Apps (e.g. Eclipse RCP apps and other enterprise apps) can invoke a local instance of RP Protocol Support that uses a locally running ISS Client UI (card selector UI).
Links
- Higgins Home
- Wiki
- FAQ
- Architecture
- Components
- Developer Resources
- Downloads