Difference between revisions of "Architecture"

From Eclipsepedia

Jump to: navigation, search
(Components)
(Replacing page with 'Each deployment configuration has its own architecture diagram. See Deployments.')
Line 1: Line 1:
__NOTOC__
+
Each deployment configuration has its own architecture diagram. See [[Deployments]].
[[Image:Higgins-v42.JPG]]
+
 
+
[[Architecture Diagram Changes]] --changes to the above diagram
+
 
+
===Components===
+
* [[Higgins Browser Extension]]
+
* [[RP Enablement]]
+
* [[I-Card Manager]]
+
* [[RP Protocol Support]]
+
* [[I-Card Selector]] (formerly 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==
+
* [http://eclipse.org/higgins Higgins Home]
+
** [http://wiki.eclipse.org/index.php/Higgins_Wiki Wiki]
+
** [http://www.eclipse.org/higgins/faq.php FAQ]
+
** [[Architecture]]
+
** [[Components]]
+
** [http://www.eclipse.org/higgins/resources.php Developer Resources]
+
** [http://www.eclipse.org/higgins/downloads.php Downloads]
+

Revision as of 23:42, 18 September 2007

Each deployment configuration has its own architecture diagram. See Deployments.