Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update tech-x summary #1

Open
wants to merge 2 commits into
base: pulledtim-patch-1
Choose a base branch
from
Open

Update tech-x summary #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21f121c
Update README.md
pulledtim May 22, 2023
9f86a01
Apply suggestions from code review
pulledtim May 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -506,12 +506,12 @@ Policy creation follows the same steps for each of them:
## Summary
Gaia-X compliant Trust and IAM framework 

This team focused on the integration between Gaia-X and i4Trust frameworks, with focus on identity and access management. The main goal was to adapt the trust-anchor service – called iSHARE Satellite – to get participant information from the OnBoarding-Portal.  
This team focused on the integration between Gaia-X and i4Trust frameworks, with focus on identity and access management. The main goal was being able to introduce new participants to a dataspace by using the Gaia-X services as trust anchor.  

The onboarding service already had the functionality to use a Gaia-X compliant Self-Descriptions for legal participant to onboard a company in an i4Trust dataspace. The piece added during the hackathon was to retrieve the information on the trusted issuers from the portal and provide it to the dataspace to be added in the Trusted Participants list. The results is that users of the dataspace can be sure they are consuming services only from trusted partners. 
The onboarding service and its IAM-Framework already had the functionality to validate and persist Gaia-X compliant Self-Descriptions for legal participants in an NGSI-LD compliant broker. During the hackathon, an [EBSI-compliant Trusted Issuers Registry](https://api-pilot.ebsi.eu/docs/apis/trusted-issuers-registry/v4#/) based on those Self-Descriptions was implemented. By using this implementation as a participant registry inside a dataspace, the onboarded company and its users can participate inside the dataspace.

Outcome & take-aways 

The team successfully shown a live demo at the end of the 2 days of hacking, where a legal representative of a company – Animal Goods Org – can issue the legal participant SD, can store it in a FIWARE wallet, and from there call the Gaia-X Compliance Service to get the compliance proof. After these steps, the legal representative can issue NaturalPerson Credentials for themselves and onboard the company in the dataspace, where Animal Goods Org is added as a trusted participant. 
The team has successfully shown a live demo at the end of the 2 days of hacking, where a legal representative of a company – Animal Goods Org – can issue the legal participant SD, can store it in a FIWARE wallet, and from there call the Gaia-X Compliance Service to get the compliance proof. After these steps, the legal representative can issue NaturalPerson Credentials for themselves and onboard the company in the dataspace, where Animal Goods Org is added as a trusted participant. 

A detailed description of this session can be found [here](https://github.com/FIWARE-Ops/tech-x-challenge). For any questions or follow-ups, the team can be reached at TODO: add contact info