Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "AIR Client+Server"

(Links)
(Links)
Line 32: Line 32:
  
 
== Links ==
 
== Links ==
* [[Solutions]]
 
 
* [http://eclipse.org/higgins Higgins Home]
 
* [http://eclipse.org/higgins Higgins Home]

Revision as of 12:43, 6 March 2008

Introduction

This solution provides an Adobe AIR based Identity Selector that runs on the local machine. It requires hosted I-Card component for I-Card management and Higgins Selector Selector components to interact with the browser.

How it works

  1. When user submits an info-card form in the browser, the browser extension intercepts the action, collect the policy string, and sends the string to Higgins Selector Selector. Higgins Selector Selector invokes the Adobe AIR-based Selector using the Connector for Adobe AIR Selector.
  2. Adobe AIR-based Selector communicates to hosted I-Card service and shows I-Card Selector UI
  3. User selects an I-Card and clicks "Send this card" button
  4. Adobe AIR-based Selector gets security token for the selected I-Card from hosted I-Card service and sends token to Higgins Selector Selector
  5. Browser extension retrieves token from Higgins Selector Selector
  6. Browser extension submits token to RP

End-User Perspective

<TODO>

Functionality

<TODO>

Setup

<TODO>

Deployer Perspective

<TODO>

Deploying

<TODO>

Configuration

<TODO>

Developer Perspective

<TODO>

Architecture

<TODO>

Building

<TODO>

See Also

Links

Back to the top