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

Compare with Current View Page History

« Previous Version 2 Next »

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

Participants

Proposers
NameOrganisation
Slavek Licehammer & Pavel BrousekCESNET
GN4-3 project team
NameOrganisationRole
Lucie KureckovaCESNETDeveloper, TIM student
Pavel BrousekCESNETMentor


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

Account linking is, in principle, a simple process of joining user’s digital identities. Users have to prove that they own two or more digital identities, which are consecutively linked together in the identity management system. CESNET has very positive feedback on ELIXIR workflow for account linking. User signs in with one identity, then with a second one, and the identities are linked. The positive feedback is coming not only from the ELIXIR community but also from users from other communities, even outside the life-science area.

The significant issue of the workflow is its user interface, which is still too complicated for users to navigate through smoothly. Because the process consists of several steps, skipping one step or leaving the linking process unfinished makes it even more prone to errors. Users need a straightforward interface that will guide them step-by-step through the whole process.


<Enter here>

Activity goals
The goal of the topic is to develop a new web application for account linking, test it with end-users and improve it based on user feedback. The application has to support a recommendation system that tries to guess linkable identities. It also has to deal with all possible situations in a user-friendly way. The situations include linking identities that already belong to different registered users or linking identities neither of which belongs to a registered user.

Activity Details

Technical details

The account linking application will work with the OIDC protocol only. Based on the AARC Blueprint architecture, the proxy component can translate other protocols to OIDC, so the account linking application does not have to handle other protocols. Most of the application logic will be standalone but it will expect an IdM system as a backend for storing linked identities.

<Enter here>

Business 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 implementation of Account linking web application would benefit

Risks

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

<Enter here>


Data protection & Privacy

An account linking service runs the risk of becoming a privacy hotspot. High standards for coding, security and quality control are required.


Definition of Done (DoD)

#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>

  • a prototype of Account linking application
  • the prototype is successfully tested


Sustainability

#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

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