You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Participants

Proposers
NameOrganisation
Hannah Short CERN
GN4-3 project team
NameOrganisationRole
AlanGÉANTCore team member
AndrejKUCore team member
MartinSURFCore team member
UrosKITCore team member


Stakeholders
Name

Organisation

Role 
Hannah ShortCERNREFEDS Representative
Nicole HarrisGÉANTHead of T&I Operations
Alex StuartJISCCommunity Representative

Activity overview

Description

This activity seeks to provide an easy-to-use, user-configurable test Identity Provider.

Activity goals

The aim of this activity is design and implement a fully functional SAML IdP that can be used to perform individual integration test by community members.

Activity Details

Technical details

This activity creates a freely available, realistic test IdP for the GÉANT community. Based on the needs of the GÉANT community, the solution may offer SAML, OIDC and supports all the latest best practices. 

In the past, there were similar offers like UnitedID or samltest.id. However, the UnitedID solution does no longer exist and samltest does not support required features like the release of R&S.  

To achieve this task, the Incubator has to define the use cases which are needed by the community. The requirements and use cases for such a service will be defined in collaboration with a group of community representatives. Potential features of such a tool are:

  • Test for a specific set of attributes
  • Create an account to save a test profile
  • An open (REST) API to configure the IdP using a (web) client

There are different potential business cases for deployment: as part of the eduGAIN support tools, by GÉANT operations or NREN hosted.

Business case

Operators need a reliable way to test their providers. This enables the early detection of errors in the configuration and increases the quality of the entities in eduGAIN in the long term.

Risks
  • It yields some difficulties to ensure the sustainability of such a service


Data protection & Privacy
  • The activity itself does not handle any sensitive data
  • The service is supposed to be used only for testing using test data
  • The design of any centrally must consider security and privacy principles


Definition of Done (DoD)
  • Community requirements and use cases are documented
  • A solution is designed, implemented and tested
  • A test deployment is made available and tested by some operators
  • A sustainability model is defined
  • The software and supporting resources are provided to the future maintainer


Sustainability
  • Design, source code and documentation is published publicly
  • A responsible party to host and manage the service will be defined

Activity Results

Results

Meetings

Date

Activity

Owner

Minutes


Stakeholder kickoff meeting



















Documents

No files shared here yet.



  • No labels