Difference between revisions of "Org.eclipse.higgins.hss"
(New page: Higgins Selector Selector architecture allows the users to choose the Identity Selector of their choice from the available selectors on their system. It also allows the developers to creat...) |
m (Higgins Selector Switch moved to Org.eclipse.higgins.hss) |
||
| (66 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Higgins Selector | + | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} |
| + | [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
| + | __NOTOC__ | ||
| + | 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: | ||
| + | * [[Connectors for Higgins Selector Switch]] | ||
| + | * [[Higgins Information Card MIME handler for IE]] or [[Higgins Browser Extension for Firefox]] | ||
| + | |||
| + | === 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. | ||
| + | |||
| + | [[Image: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 | ||
| + | |||
| + | [[Image:Ss-core-v2.png]] | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | [[Category:Higgins Components]] | ||
Latest revision as of 10:22, 26 October 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
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:
- Connectors for Higgins Selector Switch
- Higgins Information Card MIME handler for IE or Higgins Browser Extension for Firefox
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.
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
