Issuer App web-portal for EBSI - Dockerfile paths correction and absence of credentials and custom credential input and broken EBSI documentation links

[MarioScalabrino]

Hello Waltid.

I would like to install in my server a web portal for the issuer of diploma VCs on EBSI, then make it public online for a Holder wallet to download the Diploma VCs Issued.

It is not clear to me from the documentation if I should use the Issuer APP or other components.

I tried the Issuer app in the container in this documentation https://docs.walt.id/community-stack/issuer/apps/portal/overview.

Issue 1.
I had to modify the Dockerfile because the internal paths have changed and the web-portal is in another position.
in edit mode and correct the path here, comment the existing and add the second one

---

#COPY waltid-applications/waltid-web-portal/. /build
COPY waltid-web-portal/. /build

---

Once the docker was up and running in localhost, the webportal didn't have the custom credential button that the video shows. Nor any credential were loaded. It was all empty.

Issue 2.
The links to the EBSI issuer guides are broken from this page https://docs.walt.id/community-stack/issuer/api/ecosystems/ebsi/overview
The following are broken
https://docs.walt.id/community-stack/issuer/api/vc-oid4vc
https://docs.walt.id/community-stack/issuer/api/data-functions#ebsi-specific-functions
https://docs.walt.id/community-stack/issuer/api/data-functions

Could you please help on this two issues?

[MarioScalabrino]

Issue 1.
Small advance but still open.
We decided not to followup on this problem on windows and web-portal app alone.

We installed the complete stack in a ubuntu linux machine launching "cd docker-compose && docker compose up".
I had to modify nothing in the code, just minimal normal integration, version, libraries issues in Linux. In few hours it was up an running locally in the localhost in the expected ports,the webportal (7102) and the holder wallet (7010).

Unfortunately we didn't understand how to load the credentials from the repository in localhost: 7103 that is on and working. We didn't understand how to make the call and transfer the desired demo credentials in the portal nor how to do it manually,
We would appreciate to know how to reinsert the button in the video, that can load a custom VC manually just with cut and paste.

Issue 2.
Unchanged.
Links to EBSI documentation are still broken.

Waiting for your kind news

Thanks

[alegomes]

Hello Waltid.

Hi Mario!

I would like to install in my server a web portal for the issuer of diploma VCs on EBSI, then make it public online for a Holder wallet to download the Diploma VCs Issued.

Ok.

It is not clear to me from the documentation if I should use the Issuer APP or other components.

We have three different options for you:

1. Low level libraries that you could use to build your own solution from scratch.
2. Full-fledge APIs that provide you with all the backend services needed to issue and verify credentials.
3. White label apps that you can use as a scaffold to build your own products. There's and Issuer and a Verifier Portal available here.

I tried the Issuer app in the container in this documentation https://docs.walt.id/community-stack/issuer/apps/portal/overview.

Ok.

Issue 1.
I had to modify the Dockerfile because the internal paths have changed and the web-portal is in another position.
in edit mode and correct the path here, comment the existing and add the second one

#COPY waltid-applications/waltid-web-portal/. /build
COPY waltid-web-portal/. /build

Actually, it's the docker build command that is wrong and not the Dockerfile. This is what it should be:

docker build -t waltid/portal -f waltid-applications/waltid-web-portal/Dockerfile .

Once the docker was up and running in localhost, the webportal didn't have the custom credential button that the video shows. Nor any credential were loaded. It was all empty.

Yes. There was also something missing in the docker run command.

It should be:

docker run -p 3000:3000 -e NEXT_PUBLIC_VC_REPO="https://credentials.walt.id" -i -t waltid/portal

Docs updated. Thank you so much for pointing this out.

Issue 1.
Small advance but still open.
We decided not to followup on this problem on windows and web-portal app alone.

Why did you mention Windows? Did you have any specific Windows issue? If so, please let us know.

We installed the complete stack in a ubuntu linux machine launching "cd docker-compose && docker compose up".

Ok

I had to modify nothing in the code, just minimal normal integration, version, libraries issues in Linux.

Hummm. This is interesting. I'm curious to hear more from you what did you did. You shouldn't have needed to change anything. Could you please tell us more about that?

In few hours it was up an running locally in the localhost in the expected ports,the webportal (7102) and the holder wallet (7010).

Few hours?! 😱 What a terrible experience. We are so sorry about it. It should be a matter o minutes.

git clone
cd docker-compose
docker compose up

I'm very interested to hear your feedback about this first experience and where do you think the bottlenecks are.

Unfortunately we didn't understand how to load the credentials from the repository in localhost: 7103 that is on and working.

Not sure if I understood the full sentence. You started saying you couldn't load credentials but then you finished saying something "is on and working". Could you, please, rephrase, ir?

We didn't understand how to make the call and transfer the desired demo credentials in the portal nor how to do it manually,
We would appreciate to know how to reinsert the button in the video, that can load a custom VC manually just with cut and paste.

---

Do you mind opening a second issue on Github to discuss your Issue 2?

All the best,
Ale

[MarioScalabrino]

Hello Alexandre, I'll answer back on Friday.
We'll install again the whole composer system for the white label apps, taking in account what you wrote and we'll report any possible issue.
I'll also open another github issue for issue 2 as requested on friday.
Thank you
Regards

[MarioScalabrino]

Hello Alexandre we couldn't have the meeting on Friday. I'll update on the issue next Tuesday, sorry for the inconvenience.
Have a good weekend
Mario