Concept Creation for Multi-Wallet Provider Integration and BYOW Connection in SSI Issuance Flow

[jjeroch]

This feature was created by the network service committee to ensure that the scope is planned for 24.08.

Description: The purpose of this ticket is to conceptualize and evaluate the necessary modifications to the Self-Sovereign Identity (SSI) issuance flow to facilitate the support of multiple wallet providers and the option for users to bring their own wallet (BYOW). The focus is on maintaining a customer-centric design throughout the process, ensuring that the user experience is intuitive and efficient. This includes the creation of a customer journey map that details the user's interaction with the SSI system and the integration of wallet-to-wallet communication, which is an essential component of the credential issuance flow.

Possible Impacted Products:

• portal
• registration
• OSP/CoreServiceProvider
• issuance component
• gaia-x clearinghouse (?)
• EDC

Acceptance Criteria:

1. Customer Journey Map Development:

   • Construct a detailed customer journey map that captures the user experience with the current SSI issuance process, highlighting interactions with wallet providers.
   • Identify points within the journey where users can choose different wallet providers or connect their own wallet.

2. Conceptual Framework:

   • Design a conceptual framework that enables users to select from multiple wallet providers or connect their own wallet during the SSI issuance process.
   • The framework must prioritize ease of use and a clear, straightforward selection process for the user.

3. Technical Assessment:

   • Evaluate the existing technical infrastructure to understand the implications of integrating multiple wallet providers and BYOW capabilities.
   • Identify technical requirements and any potential challenges that may arise from wallet-to-wallet communication.

4. Impact Analysis:

   • Analyze how the new multi-wallet provider and BYOW features will affect existing systems and user processes.
   • Formulate a change management strategy to address any impacts identified.

5. Documentation:

   • Produce comprehensive documentation of the new concept, including visual aids like diagrams and flowcharts, and detailed descriptions of user interfaces.
   • Documentation should be clear and accessible to stakeholders with varying levels of technical expertise.

6. Regulatory Compliance and Security Assessment:

   • Verify that the new concept adheres to applicable regulations and industry standards.
   • Perform a security assessment to ensure that the integration of multiple wallet providers and BYOW does not compromise security.

Deliverables:

1. Customer Journey Map
2. Conceptual Framework Documentation
3. Technical Assessment Report
4. Impact Analysis Document
5. Comprehensive Documentation Package
6. Compliance and Security Assessment Report

Timeline:

• A detailed timeline will be established following the initial concept and assessment phase.

Resources Required:

• Access to existing SSI issuance flow systems and documentation
• User data for customer journey mapping
• ....
• ....

Risks and Mitigations:

• Risk: Integration of multiple wallet providers and BYOW may introduce complexity and user confusion.
  • Mitigation: Focus on a user-centric design approach and conduct extensive user testing to refine the interface and flow.
• Risk: Potential security vulnerabilities with wallet-to-wallet communication.
  • Mitigation: Implement robust security protocols and conduct thorough security assessments.

Additional Notes:

• The design process should be iterative, with continuous user feedback shaping the evolution of the concept.
• Collaboration with UX/UI designers is essential to ensure the interface and user interactions are optimized for a positive user experience.
• Regular updates and review sessions with stakeholders will be critical to maintain alignment and transparency.

[DanielaWuensch]

@jjeroch : Please add label "ssi" as soon as it is created as it is also relevant for SSI Expert group

[stephanbcbauer]

Hello @jjeroch , @evegufy

Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

• [ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• [ ] Please check whether the status (backlog, work in progress ...) is set correctly
• [ ] Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
• [ ] Please comment on the current status of the feature
• [ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

If you need any clarification, please get in touch, thank you very much. Stephan