Solutions/RCP Selector Solution

Introduction

This solution provides a Eclipse RCP based program which can be installed into end-user desktop machines. This program consists of the complete Higgins infrastructure stuffs (refer to the architecture section), as well as a SWT/JFace based I-Card selector, in order to give end-user a more secure way to manage i-cards, and a rich and friendly user experience of i-card selection.

The solution program runs on end-user desktop machine as a daemon process, and provides browser integration function (see the following sections) by default. On Windows platform, the intgration code will give end-user a chance to select Microsoft CardSpace or Higgins as their default i-card management and selection program. The solution program also provide integration interface to other applications (e.g. Java application) through different ways.

How it works:

1. When the program first run, it launches a card manager UI, where the 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.

Note: The HBX component referred to above is the Higgins Browser Extension for IE7 not Higgins Browser Extension for Firefox.

End-User Perspective

Functionality

<what is its functionality?>

Setup

<how do you install it?>

Deployer Perspective

<This section exists only if the solution can be deployed independently, e.g. STS. In the event that the solution consists of executables that run in more than one process, then these "sub-systems" should link to separate pages that adhere to the following structure (for example, see here>

<links to one or more pages to describe...>

<..prerequisites>

Download

<..how to obtain the .WAR, .jar, etc.>

Deploying

<..how to deploy a complete working solution>

Configuration

<..configuration files, options, etc.>

Developer Perspective

<links to one or more pages to describe...>

Architecture

<..[flow diagrams]>

<..list of components used>

Building

<..how to get the source>

<..how to build executables (jars, wars, exes, etc)>

See Also

• Solutions

Links

• Higgins Home