-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to verify credential using local setup #245
Comments
Dear @virajpatva, Could you please provide some more information about your setup?
Kind regards. |
Hi @dzarras , |
Hi @virajpatva, Thanks for the input. When using ngrok, which URL are you using to access the Verifier? Is this the same URL as Also FYI, the service deployed at https://verifier.eudiw.dev uses the The Wallet appears to be rejecting the Authorization Request from the Verifier. Without logs from the Wallet though, we can't say for sure. Hence we can only provide hints about what to check. Kind regards. |
@dzarras , I am setting up the local verifier using Docker Compose and exposing its port via Ngrok. The Ngrok URL is being used as the Here are the wallet logs: the logs read out : |
Hi @virajpatva, Thanks for the input. What you encountered has also been discussed in #231 as well. Verifier Endpoint by default generates an RSA key and uses RS256 to sign JARs. On the other hand the Wallet app has a hardcoded value and requires ES256, ES384, ES512 algorithms for JARs. This is addressed in eu-digital-identity-wallet/eudi-lib-android-wallet-core#132. (Hence why JARs signed with RS256 are rejected) What you can do to rectify this issue is to switch to Please let us know if this works for you. Kind regards. |
Hi @dzarras ,
|
Hi @virajpatva, Please consult the configuration guide here The Client Id Scheme is Concerning the Certificate and Signing Key, you have to add it to a Keystore file, and then configure the application to use it, using the corresponding environment variables (reference). Finally you'll have to update the signing algorithm using the Kind regards |
I have a same problem when i use pre-registered client_id_scheme in local setup. I am also curious why in SignRequestObjectNimbus.kt in private method asClaimSet you only set clientId and i dont see client_id_scheme being set. |
Dear @virajpatva For |
Thank you a lot for help. |
@VelikiGmaz what exactly is this second URL? |
Sorry i guess i wrote it poorly, i am looking for compatibility table between eudi-wallet and eudi-verifier so i know which tags to use for them |
@VelikiGmaz If possible please correct both links. I just noticed that both of them do not point to github.com. As for you question, unfortunately, currently no such compatibility table exists. Kind regards. |
@virajpatva Is there anything else we could help you with? If not, could you please close this issue? |
Hey again, i am going to switch x509_san_dns and try that out and create keypair for ES256 and load it. |
@VelikiGmaz Please use this service: https://registry.serviceproviders.eudiw.dev/ to get a certificate and an EC key pair that is trusted by the Wallet. |
I have created a Certificate from the mentioned link and add to repo under main/resources/ , this is my configuration:
still the issue persist. this are the logs :
|
@virajpatva As I understand it, you are using the docker compose setup. To use your own certificate you must use Volumes to make your keystore available inside the docker container. Please consult the docker compose reference documentation here: |
Hi @dzarras , I was able to load the Cert but it is still failing with the following error :
Thanks |
@virajpatva Could you provide the full stacktrace? This doesn't provide enough information. Also have you set in your environment variables the alias and password of the keypair to load? |
Hi @dzarras , I haven't set the alias , what should be value of it ? Also I have set the correct password for As requested here are the full logs :
|
@virajpatva Try opening the keystore using Keystore Explorer. The alias is name name of the entry you will see (usually the Common Name). The password of the keypair should be the same as the one of the keystore. |
Hi @dzarras , It still result same error, here is my Docker Compose Config :
this is error log :
|
Hi @virajpatva, Some pointers:
You could try and check out the example configuration here. I'm adding the Kind regards. |
Credential verification is failing on mobile after setting up the local environment and using Ngrok with this repository https://github.com/eu-digital-identity-wallet/eudi-srv-web-verifier-endpoint-23220-4-kt. The QR code for the presentation request is generated successfully, but the process fails with an error, as shown in the screenshot below.
here is log :
verifier-backend | 2025-01-30T06:32:08.784Z INFO 1 --- [or-http-epoll-2] EVENTS : Verifier initialized transaction - tx: _QpzW5bm9DQ_xxLErVBNxVEDRql2Crx4d5kHcj7h0X2foQJhiNMUHmOiNBuf7aWqc1Uaza_ZLXcw3Qadyex4kg
verifier-backend | 2025-01-30T06:32:08.784Z INFO 1 --- [or-http-epoll-2] e.e.e.e.v.e.a.input.web.VerifierApi : Initiated transaction tx _QpzW5bm9DQ_xxLErVBNxVEDRql2Crx4d5kHcj7h0X2foQJhiNMUHmOiNBuf7aWqc1Uaza_ZLXcw3Qadyex4kg
verifier-backend | 2025-01-30T06:32:24.081Z INFO 1 --- [ parallel-2] e.e.e.e.v.e.adapter.input.web.WalletApi : Handling GetRequestObject for mhpixvTNzTMKSMNrhWs-eWlcRCOv1khPOEpklu0rg7EPOqveijczSkfIz00NjqvcWSAuB24exAnIOGXZmbKSWg ...
verifier-backend | 2025-01-30T06:32:24.167Z INFO 1 --- [ parallel-2] EVENTS : Wallet retrieved Request Object - tx: _QpzW5bm9DQ_xxLErVBNxVEDRql2Crx4d5kHcj7h0X2foQJhiNMUHmOiNBuf7aWqc1Uaza_ZLXcw3Qadyex4kg
The text was updated successfully, but these errors were encountered: