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 "Architecture"
(→See Also) |
|||
| Line 1: | Line 1: | ||
| − | + | Higgins 1.0 Component Architecture | |
| − | + | ||
==Core Components== | ==Core Components== | ||
| Line 8: | Line 7: | ||
[[Core Components Changes]] --changes to the above diagram | [[Core Components Changes]] --changes to the above diagram | ||
| − | ==Core Components== | + | ===Core Components=== |
* [[RP Enablement]] | * [[RP Enablement]] | ||
* [[I-Card Manager]] | * [[I-Card Manager]] | ||
Revision as of 17:24, 7 November 2006
Higgins 1.0 Component Architecture
Core Components
Note: In this diagram "PI" means a plug-in.
Core Components Changes --changes to the above diagram
Core Components
- RP Enablement
- I-Card Manager
- HBX Support
- ISS Web UI
- ISS Client UI
- I-Card Selector Service (ISS)
- I-Card Registry
- I-Card Provider
- Token Service
- Token Provider
- Identity Attribute Service (IdAS)
- Context Provider
Client Components
Client apps and services that use these core components are expected to include:
- Higgins Browser Extension
- "Relying Party" websites that will consume identity data provided by Higgins-based services. These would use at least the "RP Enablement" component mentioned below
- Eclipse RCP apps can leverage the ISS Client UI app for authentication
- Enterprise apps that could potentially rely on one or more of: I-Card Selector Service, ISS Web UI, ISS Client UI, and Identity Attribute Service