Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Architecture"

(Higgins Clients)
(Core Components)
Line 6: Line 6:
 
[[Image:Higgins-v28b.JPG]]
 
[[Image:Higgins-v28b.JPG]]
  
 +
[[Core Components Changes]] --changes to the above diagram
 +
 +
==Core Components==
 
* [[RP Enablement]]
 
* [[RP Enablement]]
 
* [[I-Card Manager]]
 
* [[I-Card Manager]]
Line 19: Line 22:
 
* [[Context Provider]]
 
* [[Context Provider]]
  
[[Core Components Changes]]
+
==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]]
  
 
==See Also==
 
==See Also==
 
* [http://eclipse.org/higins Higgins Home]
 
* [http://eclipse.org/higins Higgins Home]
 
* [[Component Matrix]]
 
* [[Component Matrix]]

Revision as of 17:05, 7 November 2006

This page describes the architecture of the core components planned for Higgins 1.0


Core Components

Note: In this diagram "PI" means a plug-in.
Higgins-v28b.JPG

Core Components Changes --changes to the above diagram

Core Components

Client Components

Client apps and services that use these core components are expected to include:

See Also

Back to the top