Versions Compared

Old Version 38

changes.mady.by.user Niels van Dijk

Saved on

compared with

New Version 39

changes.mady.by.user Marina Adomeit

Saved on

Key

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

...

Panel
titleDescription

Research communities have a need to express and potentially share certain trust marks on IdPs and SPs. These trust marks may differ from existing trust marks issued by identity federations, or . They may be put in used to compliment existing ones, in case the federation operator does not support these, particular trust marks like e.g. in the case of SIRTFISirtfi.

This project activity tries to implement a technical solution that matches the requirements as described by the SIRTFI Sirtfi community and investigates usability of the solution for research communities and the impact of the solution of Identity to the identity federations. It also explores potential other scenarios where a similar methodology could be used, like e.g. REFEDs REFEDS MFA and in the context of the IdP self assessment tool that was developed in GN42GN4-2.

Out of scope for this activity are the questions about It does not consider itself with the questions on where and how such a tool would be used in the context of existing trust frameworks.


Panel
titleGoals

Topic Activity goals:

  • Create technical implementation based on Sirtfi + Registry documentrequirements;
  • Distill technical requirements from Sirtfi + Registry documentrequirements;
  • Create/Describe technical design;
  • Buy or build (or modify existing);
  • Improve trough sprint iterations;
  • Interact with Sirtfi working group to improve features if needed.;
  • Learn and discuss flows and usability in ‘real world’ (Collaborate with LIGO);
  • Deploy working setup so it can be tested with stakeholdersstakeholdersv
  • Explore and describe (& implement) authZ architecture in collaboration w/ Sirtfi working group.


Panel
titleBackground information

Sirtfi Registry Requirements: https://docs.google.com/document/d/1wh2SQU62zDRwlJLPFgwxmRnIq7IiVgPf76XI97Hzt80

Use User story description: https://docs.google.com/document/d/14pzjKo-QHWlGd5D0aRRzADSraPcDuf7HbUJrO_IbYqE/edit?ts=5c90ce9d

...

Panel
titleData protection & Privacy

With the federated access and adhering to basic principles of Federated Identity Management federated identity management (following DPCoCoV2 and, e.g., applicable AARC guidelines), no new issues regarding processing of personal data are foreseen.

...

Panel
titleDefinition of Done (DoD)

Work is done when the initial version for proof of concept is implemented and evaluated.


Panel
titleSustainability
At this point the The assumption is that the solution will be a software package product that can be operated by a collaborative organization or a technical partner on their behalf.
The software product resulting of this activity will be made available under appropriate open source license so development may continue even after the work finished in the GEANT project

...