Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

#Use this template to capture proposal for a new Incubator Activity - delete this line after using the template#

Participants

#Enter the persons who are submitter of the Activity - delete this line after using the template#
Panel
titleProposers


NameOrganisation
Bas Zoetekouw SURF



#Enter the persons who are participating in the team that works on this Activity - delete this line after using the template#
Panel
titleGN4-3 project team


NameOrganisationRole
HalilGRNETCore team member
MatteoKIFUTIM student
MihalySZTAKICore team member



Panel
titleStakeholders


#Enter the persons who are internal projects or external stakeholders of this Activity - delete this line after using the template#

Name

Organisation

Role 
Bas Zoetekouw SURF
tbd
Shibboleth developer
tbd
SimpleSAMLphp developer
tbd
SaToSa developer


Activity overview

Panel
titleDescription

#Please describe the high-level goal of the incubator Activity, provide an overview of the anticipated work and needed resources and skills. Please also describe how commitment from various partners is warranted. - delete this line after using the template#

<Enter here>This activity attempts to create a fully fledged dynamic test environment for new and existing federated software products to enable quick and easy integration testing.


Panel
titleActivity goals

#Please describe the goals of Activity, including what needs to be delivered, participants, the community(ies) that require a solution. Describe when the Activity is done and how to measure the success of it, in a SMART way. - delete this line after using the template#

<Enter here>The aim of the activity is to design such a test environment, identify the necessary technologies and implement a working prototype.

Activity Details

Panel
titleTechnical details

It is currently very hard to test new releases of IdP and SP software against other IdP/SP products. For example, the fix for the latest SATOSA/PySAML security vulnerability turned out to break logins from a number of IdP products, which was not discovered until the patches were tested against real-life IdPs. One solution to this problem would be a dynamic test platform, which could automatically test 'all' combinations of IdPs and SPs.

One way to solve this problem is to create an automated test environment. To make this successful a generic platform is needed on which different SP and IdP products can be plugged in. The platform would need to run a CI-like matrix testing (regularly or whenever a new product in added). A number of standard products (SSP, SATOSA, ADFS, etc) would need to be configured for automatic testing, and the platform would need to allow local development teams (for example SSP developers, or local federations which develop their own federation production) to add their own products and versions to the platform.

This activity attempts to design such a test environment. A suitable architecture for an IdP/SP continuous integration platform is to be created. This involves creating use cases and identifying technologies that support them. An iterative approach, in which use cases are successively implemented and products are integrated one after another, is intended to quickly create a functional platform. If the CI approach is successful, ready-to-use software packages can be provided using container technologies such as Docker, to deploy the entire software locally by NRENs or other parties.

#Please describe the technical details for the Activity. - delete this line after using the template#

<Enter here>


Panel
titleBusiness case

#What is the business case for the Activity? Who would be beneficiaries of the results of the Activity and what would potential business case look like if applicable? - delete this line after using the template#

<Enter here>The envisioned integration platform would enable developers across the GÉANT community to not only preempt compatibility issues with new software releases, but also flush out incompatibilities between existing IdPs/SPs that are already in eduGAIN. As a result, the quality of the software in federations and eduGAIN as well as the time to market of new products can be significantly improved.


Panel
titleRisks
  • The automated combination of all possible tools may prove to be too complex
  • We do not know exactly how well continious integration works in this scenario


#Are there risks that influence either the implementation of the activity or its outcomes? - delete this line after using the template#

<Enter here>

Panel
titleData protection & Privacy

#How do The activity does not affect data protection and privacy impact the Activity? Think about e.g. handling of personal data of users - delete this line after using the template#
<Enter here>or privacy.


Panel
titleDefinition of Done (DoD)
  • Testbed requirements and use cases are analysed and documented
  • A design and architecture for the test environment was created
  • A prototype of test environment was created and tested with various software products
  • Scripts and guidelines for automated deployment are available

#Please describe here the set of criteria that the product must meet in order to be considered finished. - delete this line after using the template#

<Enter here>


Panel
titleSustainability
  • The right strategy needs to be identified depending on the design of the testbed
  • To ensure long-term support of the supported products, the development teams responsible should be involved to maintain their own products.

#How are the results of the Activity intended to be used? If this requires further engagement, can you describe how you intent to sustain it? - delete this line after using the template#

<Enter here>

Activity Results

Panel
titleResults
#Please provide pointers to completed and intermediary results of this activity - delete this line after using the template#The activity is still ongoing

Meetings

Date

Activity

Owner

Minutes


January 1, 2017

Kickoff Stakeholder kickoff meeting

















Documents

Attachments