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 "Org.eclipse.higgins.crpps"

Line 16: Line 16:
  
 
5. HBX then send out the security token to the RP site.   
 
5. HBX then send out the security token to the RP site.   
 +
 +
== See Also ==
 +
* Solution-level description: [[RCP-based Selector Solution]]
  
 
== Links ==
 
== Links ==
 
* [http://eclipse.org/higgins Higgins Home]
 
* [http://eclipse.org/higgins Higgins Home]

Revision as of 10:44, 28 January 2008

An Identity Selector implemented as a single Eclipse RCP plugin.

The Eclipse-based identity selector UI is built up through pure SWT/JFace components, and can be packed with other Higgins infrastructure components (the configuration, secure card store provider, ISS, IdAS, and STS) to create a daemon program on desktop.

Now the HBX (both IE and Firefox) will not provide any UI. It only need to listen to the user's form submitting action, and send the policy string to the RCP I-Card selector process, which finially returns the security token.

The complete workflow is listed here:

1. When the program first run, it launches a card manager UI, where user can manage the I-Cards s/he has. The user can minimize the program as a system tray, and start it at any time s/he wants. The program also opens a socket to listen to the HBX requests.

2. When user submit a info-card form in IE, the HBX intercept the action, collect the policy string, and send the string to the RCP program through the socket.

3. The RCP program then launch the RCP based I-Card selector UI, and user can use and send card in this UI. Here User can not shift to other applications, as the I-Card selector UI will cover the desktop with a half-transparent mask, and only the I-Card selector workbench is active.

4. Once the RCP program receives the security token from STS, it send the token to HBX through the socket connection.

5. HBX then send out the security token to the RP site.

See Also

Links

Back to the top