Q&A- Tec: Credential Revocation

[MyriamLara]

Another topic that we want to share with you is regarding the revocation of a credential. We share evidence with you (images 4 and 5).

Image 4

Image 5

This error is always triggered when trying to revoke the credential.

[alexfigtree]

@MyriamLara What is running on running on port 4008? Could you please show us an error log from the relevant microservice?

[MyriamLara]

@alexfigtree

el contenedor de status en el puerto 4008 esta corriendo pero desde payload no lo alcanza a servidor por fetch:
y no alcanzamos a hacer ninguna solicitud

Por lo tanto nuestra propuesta es que mejor usen axios en lugar de fetch
https://www.npmjs.com/package/axios

[jchartrand]

@MyriamLara

Could you show us your docker compose file and any .env files? Taking out the secret parts of course.

In particular, we want to see what your GitHub configuration for the status list looks like. If you'd rather not post it here in this issue, feel free to email me.

Thanks!

[AngelOCrz94]

I attach the versions and environment variables that we use to test the application and we cannot revoke the credential. Can't find the container. I know there is another URL that works, but we don't want to depend on the external service. Solo status of the container. I tried it directly on postaman and the service works. In the payload backend it cannot be linked. You must see some problem with the IP of the containers or ports. Check it. Greetings

dcc_admin_dashboard.zip

[kayaelle]

@jchartrand - would you look into this issue? Could it be related to the version of the software being used?

[jchartrand]

@AngelOCrz94 I'm not sure if you meant to include the .env files in the zip? I just see the docker compose file. You could email them to me if that's easier/better.

[AngelOCrz94]

@jchartrand in a moment send you to email this files .env

[AngelOCrz94]

I not have shared configuration is own tec. Because no found the revocation.

[jchartrand]

@MyriamLara @AngelOCrz94

Could you try changing the env variable called STATUS_URL to: http://status:4008 (you had it set to http://localhost:4008) and then try revoking a credential again?

Thanks!

[MyriamLara]

@jchartrand

The adjustment that was indicated to us has been made and the revocation is now working successfully, however now we have the following doubts:

1.- Is it correct to make this value change?; That is, so we are no longer using the status container service?

2.- We understand that it should work with the status container service (which does not work even locally) and not with an external service (http://status:4008), and if we are going to use an external service What is the point of creating the container if another service is going to be used?

[jchartrand]

@MyriamLara

Good question. Yes, it is still using the local status container service.

http://status:4008 is the address for the service within the docker compose network. It is one of the very cool features of docker compose that lets the containers within the compose network talk to each other. The docker compose network knows to resolve http calls to 'status' to the local service container.

[alexfigtree]

@AngelOCrz94 confirms that this issue is resolved during a team meeting on 6/14/24. Closing this issue.