Table of Contents
#Use this template to capture proposal for a new Incubator Activity - delete this line after using the template#
Participants
Panel | ||||
---|---|---|---|---|
| ||||
|
Panel | |||||||||
---|---|---|---|---|---|---|---|---|---|
| #Enter the persons who are participating in the
| that works on this Activity - delete this line after using the template#||||||||
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
#Enter the persons who are internal projects or external stakeholders of this Activity - delete this line after using the template#
|
Activity overview
Panel | ||
---|---|---|
| ||
#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> | ||
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. |
Panel | ||
---|---|---|
| ||
#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 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
Panel | ||
---|---|---|
| ||
#Please describe the technical details for the Activity. - delete this line after using the template# <Enter here>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. |
Panel | ||
---|---|---|
| ||
From the view of authentization proxy is the benefit for consolidating and for user is benefiting in a way he can login with any of his accounts. The migration between the home organization would become very simple. And because of linking we can use multiple attributes from all the accounts. |
Panel | ||
---|---|---|
| ||
It might happen that someone works already on a similar project or publishes before the activity ends. Another one is that the application wont be used outside of the Perun project. Another risk is with the self-sovereign identities the account linking won't be needed anymore. | ||
#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> | ||
Panel | ||
| ||
#Are there risks that influence either the implementation of the activity or its outcomes? - delete this line after using the template# <Enter here> |
Panel | ||
---|---|---|
| ||
#How do 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>Application is not the privacy hotspot itself, other components will be. Application will be designed to work with the smallest amount of data. The data will be stored at backend, which is not part of the application. |
Panel | ||
---|---|---|
| ||
#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 | ||
---|---|---|
| ||
#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>The application will be part of the ecosystem of Perun. |
Activity Results
Panel | ||
---|---|---|
| ||
#Please provide pointers to completed and intermediary results of this activity - delete this line after using the template#A working prototype including architecture documentation was created. |
Meetings
Date | Activity | Owner | Minutes | |
---|---|---|---|---|
15.10.21 | Incubator on hands | Niels van Dijk | ||
22.02.22 | Public demo | Niels van Dijk | ||
03.05.22 | Final demo | Niels van Dijk | January 1, 2017 | Kickoff meeting |
Documents
Attachments