Skip to main content
Jump to: navigation, search

Difference between revisions of "Org.eclipse.higgins.hss"

(Architecture)
 
(5 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
=== Service ===
 
=== Service ===
 
[[Higgins Selector Switch]] is responsible for:
 
[[Higgins Selector Switch]] is responsible for:
* Accepting I-Card token requests from [[Higgins Browser Extension]]
+
* Accepting token requests from [[Higgins Browser Extension]]
 
* Dispatching token request to registered selector through selector connector
 
* Dispatching token request to registered selector through selector connector
 
* Returning token from registered selector to browser
 
* Returning token from registered selector to browser
Line 29: Line 29:
 
[[Image:Ss-core-v2.png]]
 
[[Image:Ss-core-v2.png]]
  
=== Used By ===
 
* See [[Higgins 1.1 Plan]] for what selector variants use the [[Higgins Selector Switch]]
 
  
=== Links ===
 
* [[Installer for Higgins Selector Switch]]
 
* [http://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/app/org.eclipse.higgins.tcpserver/installer/installer.exe Higgins Selector Switch download]
 
  
[[Category:Higgins Developer Info]]
+
 
 +
 
 
[[Category:Higgins Components]]
 
[[Category:Higgins Components]]

Latest revision as of 09:22, 26 October 2009

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

The Higgins Selector Switch is a switching component that sits between a browser add-on on the one hand and one or more Identity Selectors on the other. The user decides what their "current" selector is. The browser requests a security token from the selector switch that then passes this request on to the current selector. It provides an app/UI to allow the user to change their default selector. It uses a "connector" architecture that allows developers to create new connectors for new Identity Selectors.

Version

The Higgins Selector Switch is being developed for Higgins 1.1

Service

Higgins Selector Switch is responsible for:

  • Accepting token requests from Higgins Browser Extension
  • Dispatching token request to registered selector through selector connector
  • Returning token from registered selector to browser
  • Registering a default selector from available selectors

Depends on:

Architecture

The diagram below shows the relationship between two different browsers, the Higgins Selector Switch, the connectors and the Card Selectors. As you can see different connectors use different techniques to invoke/launch their associated Selector. The connector that launches CardSpace, for example, uses a DLL, whereas the connector that launches the AIR Selector uses a TCP socket.

Hss-v2.png

Note: at present there is no connector for the RCP Selector

Shown below are the utility sub-components that launch the selector switch on system startup as well as provide the UI to allow the user to change his/her choice of current selector

Ss-core-v2.png

Back to the top