Error while using wallet api from Swagger UI #83
-
I am running the wallet, issuer and verifier API as stated in this link. https://docs.oss.walt.id/wallet/api/setup/open-source. Then, I start a credential exchange flow in the issuer API using the following endpoint: /openid4vc/jwt/issue Then, I am trying to use the openid credential offer link I obtained from above endpoint to these two endpoints in the wallet API. /wallet-api/wallet/{wallet}/exchange/resolveCredentialOffer and /wallet-api/wallet/{wallet}/exchange/useOfferRequest. But I get the following errors in the attached file: I don't fully understand whether I need to use another method to use these endpoints from Swagger UI. Can you help with this? Also, I do not get the same error when I run the identity repo with the following commands : |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
yes, with docker compose the reverse proxy is done for you it might be easier to create a network and run the containers within that network so the setup would look smth. like this:
Now, when generating an offer request url it would look like:
Notice More on docker networking can be found at https://docs.docker.com/network/network-tutorial-standalone. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your response @mikeplotean. After doing what you said, the credential issuance worked as expected, but this time I started getting an error while trying to do verification of the verifiable credential. I am using the following endpoint from wallet API. /wallet-api/wallet/{wallet}/exchange/usePresentationRequest Wallet API gives an error as you can see in the attached file. I do not get the error when I run the APIs using docker compose, but I get the error when I run the containers in standalone. Can you help with that? |
Beta Was this translation helpful? Give feedback.
-
This forum is no longer being monitored. Please, if you still need our help, submit your question as a Community Stack issue. All the best |
Beta Was this translation helpful? Give feedback.
yes, with docker compose the reverse proxy is done for you
but when running the containers standalone, you need to know the address of the container to be able to talk with it
which means the
issuer-service.conf
andverifier-service.conf
should be updated to those specific ip addressesit might be easier to create a network and run the containers within that network
this makes it possible to reference the container by name (aka automatic service discovery)
so the setup would look smth. like this: