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 "Milestone 1.0M8"

(Existing Deployments)
(New Supported Deployments)
Line 23: Line 23:
 
* Changes to HBX to support this (see H2 or H3 IdA here: [[Deployments]])
 
* Changes to HBX to support this (see H2 or H3 IdA here: [[Deployments]])
  
==New Supported Deployments==
+
==Deployments==
By this milestone we will have the following deployments documented as to how to build them and in some cases hosted as a test service on an Eclipse Foundation server. See [[Deployments]] for the definition of each of these.
+
See [[Deployments]] for the definition of each of these.
  
 
===CardSpace-interoperable Identity Provider/STS [Nearly Done]===  
 
===CardSpace-interoperable Identity Provider/STS [Nearly Done]===  

Revision as of 18:44, 1 May 2007

Date: Apr 15 Handy shortcut to create a new Higgins Bugzilla entry. See all open items

Highlights

Summary: "Early-Alpha"

DONE

  • All components:
    • All core EPL code has cleared legal issues so that we may commit code abhi
    • Have up to date wiki pages (at least the first page!)
    • All component external interfaces have been reverted to Java 1.4 (e.g. For ISS/RPPS 176044 abhi)
  • Work begins on a C# ISS Client UI

ALMOST DONE

  • All components:
    • Exist (except ISS Client UI) --only missing IdAS Registry
    • As many as possible are built nightly [Need to add "incubation" string]
    • Have documented build instructions (Note: we will not delay this milestone waiting for all 3rd party libraries to clear Eclipse IP review--we will document where to go get these 3rd party libraries if we must)

NOT DONE

  • All components:
    • Exist (except ISS Client UI) --actually we *do* have ISS Client UI in C++
    • Support basic functions
  • New deployments (see below)
  • Changes to HBX to support this (see H2 or H3 IdA here: Deployments)

Deployments

See Deployments for the definition of each of these.

CardSpace-interoperable Identity Provider/STS [Nearly Done]

  • See definition
  • Complete build instructions Daniel and MikeM
  • Get this running on the Eclipse Fedora 5 VM MikeM
    • Paula, BrianC, Daniel are all working on documenting this
    • Hosted on Eclipse Foundation server

H1 Identity Agent

  • see (definition)
    • This deployment needs an owner (SergeyY, probably)
    • Hosted on Eclipse Foundation server
    • Functional equivalence with Microsoft CardSpace(TM) client (though hosted)
    • We can begin testing interoperability with RPs and IdPs that work with CardSpace

H3 Identity Agent [Andy(Novell)]

  • See definition
  • Developers have been asking for this deployment documented and running on a local Tomcat server
  • Need to decide if this is do-able in M0.8 timeframe

RPPS Web Service


RSS-SSE RP Test Application

Nightly Builds [Each Component Owner]

  • Status: As you can see here we currently only build IdAS nightly (or stable-y)
  • Another barrier is waiting for Eclipse IP review
  • Planned additions: all Components
  • Flesh out this page Nightly Component Builds [Valery]

Components

RSS-SSE RP Test App

HBX [Maxim]

  • HBX Startup Maxim (with help from Andy Dale)
  • Add the ability to handle CardSpace requests to the Zurich HBX 176037 abhi
  • Add proper handling of SOAP fault messages to UI code 176038 abhi
  • Handle Memory and Garbage Collection issues for generated-UI structures 176039 abhi
  • Allow HBX launch ISS Client UI for H2 deployment scenario

I-Card Manager

ISS

  • Handle parsing and matching of CardSpace policies 176033 abhi
  • Improvements to error handling for bad policies 176034 abhi
  • Deployability on machines other than those around Zurich 176035 abhi

RP Protocol Support [SergeyY]

RP Protocol Support-Zurich [Abhi]

  • Handle generation of SOAP faults with good messages on errors 176041 abhi
  • Make RPPS easily deployable for other clients 176035 abhi
  • The RPPS we have built sends SOAP messages. We have written a wsdl file to describe the messages. However, it uses an ad-hoc method for parsing and handling the messages because I found the Eclipse tools for building web services from wsdl to be buggy and frustrating to debug. Thus, improving the robustness of our rpps by using more standard ws tools might be a goal.

I-Card Registry [Valery]

I-Card Providers [SergeyL]

IdAS [Jim]

  • IdAS Registry refactoring 175630 163366
  • Refactor update operations 167978
    • Add methods for creating attribute values 163428
    • Make create*() methods consistent 163429
    • Go through each operation and document what atomicity means for each 171290
  • Invent string format for IFilter 171328
  • Change IContext.open to use JAAS-like callback; get rid of 'getOpenPolicy' (subsumed by callback handlers and interactions) 164048
  • De-evolve IdAS interfaces to Java 1.4 171293
  • Build Issues:
    • Versioning on jar name

Jena Context providers [SergeyL]

  • Jena-based provider (uses HSQLDB) [waiting on IPzilla] 152856 SergeyL
    • Implement user authentication and data isolation. 175561 SergeyL
    • Integration dependency: this cp can't be integrated with the existing IdASRegistry until that registry is refactored

Links

Back to the top