Difference between revisions of "Architecture"

Revision as of 04:43, 19 February 2007

Higgins 1.0 Component Architecture

Core Components Changes --changes to the above diagram

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).

@@ Line 2: / Line 2: @@
 Higgins 1.0 Component Architecture
-==Core Components==
+[[Image:Higgins-v34.JPG]]
-''Note: In this diagram "PI" means a plug-in.'' <br>
-[[Image:Higgins-v33f.JPG]]
 [[Core Components Changes]] --changes to the above diagram
-===Core Components===
+===Components===
+* [[Higgins Browser Extension]]
 * [[RP Enablement]]
 * [[I-Card Manager]]
@@ Line 21: / Line 20: @@
 * [[Context Provider]]
-==Client Components==
+===Clients/Consumers===
 Client apps and services that use these core components are expected to include:
-* [[Higgins Browser Extension]]
+* Relying Party (Service Provider)s can use the "RP Enablement" component to add support (e.g. to validate tokens) for identity protoocols
-* "Relying Party" websites that will consume identity data provided by Higgins-based services. These would use at least the "RP Enablement" component mentioned below
+* 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).
-* 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==