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

Compare with Current View Page History

« Previous Version 15 Next »

Participants

Proposers
NameOrganisation
Jule ZieglerDFN-LRZ
GN4-3 project team

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

NameOrganisationRole



















Stakeholders

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

Name

Organisation

Role 






Activity overview

Description

This activity constitutes to be the follow-up activity of the topic Second Factor Authentication - Distributed Vetting (see: https://wiki.geant.org/x/zLAuBw) of the previous Incubator cycle. It investigates analogously to the preceding cycle how identity vetting and token registration can be scaled for second factor authentication scenarios where participants are distributed over EU and beyond and thus takes into account the report which was delivered as part of the first Incubator cycle.

As part of this activity a specific flow - based on a community based approach - will be investigated. It takes into account the concept of the Web of Trust which is also used in (Open)PGP to establish a binding between a key and its owner. While this mechanism typically does not work well in broad user groups, it is very well suited to distribute trust between small groups where a pre existing trust fabric is already in place, as we typically have in research communities. What seems to be missing is a means to make this trust network auditable and transparent. In order to make the trust network transparent, this activity seeks to identify/develop tools to support this flow.

Activity goals
  • Workflow specification based on a community based approach (i.e. either in text format and/or graphical visualization such as BPMN flow(s))
  • Report on Identification of tools (e.g. REMS) to support the flow
  • Example implementation of at least 1 such a workflow
  • Demonstration at relevant venue
  • Describe how the vetted identity may be used in common authN and AuthZ systems like eduTEAMS

Activity Details

Technical details

Based on the specified flow, tools to support and implement the flow need to be identified.

The following outputs of the previous Incubator cycle will be taken into account:

Business case
Many services, especially in LifeSciences have a need for Second Factor Authentication (2FA). The quality of the LoA of the 2FA solution depends heaviliy on the quality of the token vetting. Validating the tokens however is potentially a costly effort in a distributed scenario.
Risks
  • Keep the community based approach in this iteration as simple and user friendly as possible in order to avoid complexity which might lead to incomplete work
  • Solution might not fulfill 100% of the use cases


Data protection & Privacy

Personal data which is processed during the act of identity vetting must be reduced to a minimum and transmitted/stored by using cryptographical means.


Definition of Done (DoD)
See activity goals


Sustainability
  • Intended to be used in the scope of research communities
  • Engagement with eduTEAMS task and Stepup solution

Activity Results

Results
#Please provide pointers to completed and intermediary results of this activity - delete this line after using the template#

Meetings

Date

Activity

Owner

Minutes

January 1, 2017

Kickoff meeting



















Documents

No files shared here yet.



  • No labels