trustchain-oc1-orchestral/idhub-docker
Archived
10
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

update README with current pilots and instances

Browse source
This commit is contained in:
pedro 2024-02-06 15:33:13 +01:00
parent a355e270b1
commit b791ee5c85
1 changed files with 24 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
README.md
View file

@ -1,22 +1,35 @@
# Docker deployment of IdHub and tools
## About the pilots that this repository deploys
## About the pilots and instances that this repository deploys
### Pilots
- **XO9B**:
- Instances:
- https://idhub1-xo9b.demo.pangea.org
- https://idhub2-xo9b.demo.pangea.org
- Motivation: The aim is to support an accreditation program for vulnerable people, exploring the value of using verifiable credentials to get services/benefits.
- Scenario: A vulnerable family obtains a benefit (internet connection fee discount) by presenting a verifiable credential to a connectivity provider entity.
Actors-> **XO9B**: IdHub1 (acting as a user wallet for families holding credentials issued by a social support organisation), **Connectivity provider entity**: Demo portal, IdHub2 (acting as verifier). The verifier portal incorporates verification capabalities and support to establish an OIDC4VP dialog with the user wallet for credential presentation (accreditation).
- **Setem**:
- Instances:
- https://idhub1-setem.demo.pangea.org
- https://idhub2-setem.demo.pangea.org
- Motivation: Since SETEM is a federation, members of one of the federated entities (Setem BCN) can accredit their membership to other federation members (Setem Madrid) presenting a verifiable credential to obtain a discount.
Actors-> **Setem BCN**: IdHub1 (acting as a user wallet for their members holding credentials issued by Setem BCN), **Setem Madrid**: Demo portal, IdHub 2 (acting as verifier). The verifier portal incorporates verification capabilities and support to establish an OIDC4VP dialog with the user wallet for credential presentation (accreditation).
- **Lafede**:
- Instance:
- https://idhub1-lafede.demo.pangea.org
- Motivation: Implementation of dual EIDAS1 and EIDAS2 compliant attestations as signed PDFS with public verifiable credentials exported as QR codes embedded in these documents. Member organisations and related persons of the Lafede federation request membership and training certificates.
Actors-> **Lafede**: idHub
- **Pangea**:
- Instances:
- https://idhub1-pangea.demo.pangea.org
- https://idhub2-pangea.demo.pangea.org
- Motivation: The case of Pangea as a web/internet service provider, with member organisations that receive services. These organisations have allocated several resources units (mail accounts, blogs, etc.). Only authorised users with a specific role should be able to access the Musician (Administration Control Panel of resources).
- Scenarios:
- Scenario 1-> 'Login with Organisation A (Idp)'. The staff members of organisation A, with the appropiate role, can authenticate themselves by providing their organisation credentials (username and password) to access a service in Pangea (Musician).
@ -28,8 +41,17 @@
- Scenario 2-> 'Present a verifiable credential'. The staff members of organisation A, with the appropiate credentials, present them to Pangea in order to access the Musician service.
Actors-> **Pangea**: IdP (goauthentik), IdHub (as verifier), Musician, Orchestra (with also nginx API rproxy). **Organisation A**: IdHub (as user wallet)
- **generic**: https://idhub.demo.pangea.org
- Motivation: For demo purposes, for showing other people different than the intended pilot what we do. It is currently similar to lafede pilot
- **test**: intended for software quality such as testing, CI/CD, etc.
### Instances
- **autotest**:
- Instance: https://idhub-autotest.demo.pangea.org
- Motivation: regenerated on each commit, intended for automated and fast testing
- **nightly**:
- Instance: https://idhub-nightly.demo.pangea.org
- Motivation: intended for manual testing
## Installation