Hello,
we are a development team from the University of Innsbruck, and our goal is to provide students with a one-click solution for uploading their micro-credentials to Europass.
Currently, we provide students with a downloadable PDF signed using a PAdES signature. Our next step is to integrate EDC Infrastructure services directly into our workflow.
Our plan is to use your Docker deployments, primarily the issuer and wallet services.
We would like to know whether it is possible to use these Docker services within our production environment to issue, seal/sign, and transfer micro-credentials from our server to the student's Europass account. Alternatively, is the implementation provided in your open-source project intended only as a reference (“how-to” example), rather than a production-ready deployment solution?
Our credential data will follow the ELM specification so that we can generate the required signed JSON-LD credentials.
We have a few questions:
- Are there any restrictions regarding production deployment of the issuer and wallet Docker services?
- Is it possible to upload or transfer credentials from our server directly to a student's Europass account?
- Are there architectural or permission-related limitations we should be aware of before implementing this workflow?
- Are there recommended practices for universities integrating EDCI services into existing student platforms?
Thank you in advance for your guidance.
- Etiquetas
- implementation
- Inicie sesión para publicar comentarios
Comentarios
En respuesta a Dear Ioannis, Thank you for… por Luisa Cabral
Dear Luisa, thank you very much for the clarification!
Dear Ioannis,
Thank you for your question.
For the use case you describe the Docker-based EDC components can be used as the basis for a deployment that processes ELM-compliant data, seals and issues credentials, and generates the corresponding JSON-LD credential output.
The Docker setup provided in the documentation contains the core EDC components and can serve as the foundation for your own implementation.
However, it is important to note that it is not an exact replica of the European Commission's production environment. The Commission's deployment relies on additional Commission-managed services and infrastructure components, including identity and authentication services (i.e. EU Login). As a result, organisations deploying the open-source solution are expected to configure and operate their own supporting infrastructure where required.
Regarding direct delivery of credentials to learners, this is possible through the available wallet deposit API endpoints. Credentials can be deposited directly into a learner's existing Europass wallet provided that the issuer knows either the learner's EU Login Unique Identifier (uid) or the email address associated with the learner's EU Login account. When one of these identifiers is available, credentials can be delivered directly to the recipient's existing Europass wallet without requiring manual upload. Credential issuers can also opt to create temporary wallets when they issue EDCs to a learner's (institutional or school) email address that does not have a Europass wallet linked to it. In such cases, the credential is deposited into a temporary wallet. The learner can claim this wallet for permanent use, or download the credential to store offline or upload it to an existing personal Europass wallet.
There are no additional mandatory Europass services or APIs that must be integrated beyond what is described in the documentation. However, organisations choosing to deploy the open-source components are responsible for the operation, security, maintenance, monitoring and scalability of their own environment.
Please note that while the EDC Support Team can provide guidance regarding EDC and ELM specifications, support for custom deployments, infrastructure design and other operational aspects of self-hosted implementations is limited.
If you haven't done so already, we recommend consulting the following resources:
We hope this helps with your evaluation.