Gaia-X VCs storage inside customer wallet

[jjeroch]

Summary: This implementation aims to transition the storage of Gaia-X VCs from a centralized database to a decentralized model where credentials are stored directly in the customer's wallet. This change will empower users with direct control over their credentials and align with privacy and decentralization principles.

Objective: The goal of this implementation is to modify the current data flow where Gaia-X Verifiable Credentials (VCs) are stored centrally in the portal database (only). The new approach will involve forwarding these credentials to the individual wallet instances of their respective holders, thereby enhancing privacy and control for users.

Change Description:

• High-Level Overview: The current system logic will get enhanced to enable the direct transfer of VCs from the issuing authority to the customer's wallet instance. This will bypass the central portal database, which currently acts as an intermediary storage point.
• Details of the Change:
  • Develop a secure transfer protocol to ensure the safe transmission of VCs from the central system to the customer wallet. - //already done, we use the existing protocols and endpoints
  • Implement wallet APIs that can receive and store VCs, ensuring compatibility with Gaia-X standards. - //already done, we use the existing endpoints
  • Modify the central portal's credential issuance process to redirect VCs to the appropriate wallet endpoint.
• Impact Analysis:
  • The central portal database will no longer store VCs, reducing data liability.
  • Customers will gain immediate access to their VCs without relying on a centralized repository.

Impacted Components:

• Central portal database (modification to VC storage and retrieval processes)
• Wallet instances (no change, already fully enabled but will be a part of the tests)

Acceptance Criteria:

• VCs are no longer stored in the central portal database post-issuance.
• VCs are successfully transmitted to and stored within the customer's wallet instance.
• The system complies with all relevant Gaia-X privacy and security standards.

Test Scenarios:

1. Credential Issuance and Transfer:
   • Issue a VC to a test wallet and verify that it is not stored in the central database.
   • Confirm receipt and integrity of the VC within the test wallet.
2. Wallet Storage and Management:
   • Test the wallet's ability to store multiple VCs and handle retrieval requests.
   • Validate the security features of the wallet, such as encryption and access controls.
3. Error Handling and Recovery:
   • Simulate transfer failures and ensure the system can retry or revert transactions appropriately.
   • Verify that the system logs and alerts for any issues during the VC transfer process.

Additional Notes: Features that do not meet these outlined criteria will not be considered for prioritization in the upcoming PI planning. It is essential that all development adheres strictly to the Gaia-X framework guidelines to ensure a seamless and secure integration into the customer wallet.

[jjeroch]

storage of unsigned credential to be discussed

[stephanbcbauer]

Was presented in the open planning ⇾ currently no team behind it. ⇾ no milestone set in open planning