LionShare: SFU Surrey Software Development Plan

Version 1

Dr. Marek Hatala

Simon Fraser University Surrey

May 13, 2004

Project Workpackages and Tasks

The SFU Surrey work program includes two milestones: Milestone-1 at the end of the 9th month, and Milestone-2 at the end of the 15th month. At the end of the 9th month the design of the security into ECL will be completed, at the end of the 15th month the design of the secure eduSource gateway will be finished.

Workpackage 1: Management

This workpackage is responsible for managing the SFU part of the project.

Task 1.1 Project Management

Partners involved: SFU, PennState

Duration: M1 ... M24

Objective: Manage the project

Inputs: Information from the project partners and the project director.

Expected results: Coordinating work towards achieving the project objectives. Communication to the project director.

Deliverables: No Deliverables

Task 1.2 White Paper

Partners involved: SFU

Duration: M1 ... M7

Objective: Outline the objectives of the project in relation to the broader project context.

Inputs: Previous work, project proposal.

Expected results: Positioning of the work with respect to the overall project objectives and need in the wider community. Providing outlook for the technical solution to meet the objectives.

Deliverables: The white paper document.

Task 1.3 SW Development Plan

Partners involved: SFU

Duration: M1 ... M7

Objective: Plan stages of the development and their interrelations to meet project objectives..

Inputs: Project proposal, white paper, early prototyping and consultations..

Expected results: Detail tasks with specific timeline and assigned resources..

Deliverables: This Document.

Workpackage 2: ECL Security

This workpackage designs and implements a security layer into ECL protocol and connecting midleware

Task 2.1 Review of security mechanisms

Partners involved: SFU

Duration: M6 ... M7

Objective: Map the area of security standards and approaches.

Inputs: Various, Shibboleth development group.

Expected results: Understanding of the options for design of the ECL security layer.

Deliverables: Internal report

Task 2.2 ECL security design

Partners involved: SFU, PennState

Duration: M8 ... M9

Objective: Design the security layer in ECL.

Inputs: Task 2.1, LionShare use cases.

Expected results: Detail design of the ECL protocol with security features, including details about binding security with SOAP protocol and mechanism for obtaining certificates, and checking their validity using Shibboleth like mechanism. The design will be compatible with the security solution for the Gnutella protocol.

Deliverables: Design document.

Task 2.3 Secure ECL connector

Partners involved: SFU

Duration: M10 ... M12

Objective: Extend implementation of the ECL connector to support security.

Inputs: Task 2.2, existing ECL connector.

Expected results: The security mechanism designed in Task 2.2 will be implemented into the Java ECL connector. The implementation will hide the details of the security and its binding to the protocol. The security mechanism will be available via API.

Deliverables: Secure ECL Connector (code in LionShare CVS - module name "ecl-secure-connector").

Extended Deliverables: Shibboleth plugin for Certificate Authority, IdP endpoint and impersonation service. (code in LionShare CVS - module name "lionshare-eclidp-plugin"), IdP installation document.

Task 2.4 Gateway security design

Partners involved: SFU, PennState

Duration: M13 ... M15

Objective: Investigate and design mechanism for crosswalks between secure protocols.

Inputs: Task 2.1, Task 2.2

Expected results: Investigate the possibilities for mapping between security mechanisms. Design mechanism for secure ECL gateway.

Deliverables: Design document.

Task 2.5 Secure ECL Gateway

Partners involved: SFU

Duration: M16 ... M23

Objective: Extend implementation of the ECL gateway to support security.

Inputs: Task 2.4, existing ECL gateway

Expected results: The security mechanism designed in Task 2.4 will be implemented into the ECL gateway framework. The implementation will provide gateway developers with the utilities to develop crosswalks between security mechanism used in mapped protocols.

Deliverables: Secure ECL gateway (code in LionShare CVS - module name lionshare-ecl-gateway) (Install document)(Code implementation document)

Workpackage 3: Enabling LionShare with Secure ECL

This workpackage designs and implements secure connectivity between LionShare network and other repositories and networks.

Task 3.1 Architectural cases

Partners involved: SFU

Duration: M4 ... M6

Objective: To investigate and recommend possible connectivity between LionShare and other repositories and entities.

Inputs: Various

Expected results: The output of this task will clearly indicate advantages and disadvantages of several option of connection between LionShare network, OKI enables repositories and tools and ECL network. The final connecting architecture will be recommended.

Deliverables: Report.

Task 3.2 OKI/ECL plugin

Partners involved: SFU

Duration: M2 ... M5

Objective: Investigate the feasibility of merging two approaches.

Inputs: ECL Connector, DR Search (OKI DR OSID application)

Expected results: Early prototype merging search functionality of ECL and DR OSID.

Deliverables: Prototype application (code in LionShare CVS - module name ecl-repository-osid).

Task 3.3 Secure OKI/ECL plugin

Partners involved: SFU

Duration: M13 ... M15

Objective: Develop and OKI/ECL plugin that provides a secure access to ECL network from OKI OSID enabled applications..

Inputs: Secure ECL Connector (Task 2.3), OKI/ECL Plugin (Task 3.2)

Expected results: Middleware component providing OKI OSID enabled applications with secure access to the ECL network. The plugin will make use of DR, AuthN and AuthZ OSIDs.

Deliverables: Secure OKI/ECL plugin - middleware component

Task modified: This task was replaced with extending the functionality of ECL to funtion with SASL-CA and LS IdP endpoint. (extension of Task 2.3) (code - refer to the deliverables in Task 2.3)

Workpackage 4: Design and Implementation Guidelines

The guidelines for technology adopters will highlight the important implementation decisions for connecting repositories and other networks to the secure ECL network.

Task 4.1 Guidelines v.1

Partners involved: SFU

Duration: M13

Objective: Provide guidelines fro implementing secure ECL connector.

Inputs: Secure ECL Connector design and implementation (Tasks 3.2 and 3.3)

Expected results: First version of the guidelines document.

Deliverables: The guidelines document.

Task 4.2 Guidelines v2

Partners involved: SFU

Duration: M24

Objective: Provide guidelines fro implementing secure ECL gateway.

Inputs: Secure ECL gateway design and implementation (Tasks 3.4 and 3.5)

Expected results: Final version of the guidelines document.

Deliverables: The guidelines document