We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
errorRedirectUri
When you try setting the errorRedirectUri for a verification request, it always end up using the sucessRedirectUri instead.
sucessRedirectUri
You can try your own documentation example to reproduce the error: https://docs.oss.walt.id/verifier/api/vc-oid4vc
curl -X 'POST' \ 'https://verifier.portal.walt.id/openid4vc/verify' \ -H 'accept: */*' \ -H 'authorizeBaseUrl: openid4vp://authorize' \ -H 'responseMode: direct_post' \ -H 'successRedirectUri: https://example.com/success?id=$id' \ -H 'errorRedirectUri: https://example.com/error?id=$id' \ -H 'Content-Type: application/json' \ -d '{ "request_credentials": [ "VerifiableDiploma" ] }'
I assume the issue is in the following function verify in the file https://github.com/walt-id/waltid-identity/blob/main/waltid-verifier-api/src/main/kotlin/id/walt/verifier/oidc/VerificationUseCase.kt
Thank for your help!
The text was updated successfully, but these errors were encountered:
fix: GitHub issue #290
f86a2f4
Merge pull request #301 from walt-id/fix/#290
fe9a92d
This issue has been marked as stale.
Sorry, something went wrong.
No branches or pull requests
When you try setting the
errorRedirectUri
for a verification request, it always end up using thesucessRedirectUri
instead.You can try your own documentation example to reproduce the error:
https://docs.oss.walt.id/verifier/api/vc-oid4vc
I assume the issue is in the following function verify in the file https://github.com/walt-id/waltid-identity/blob/main/waltid-verifier-api/src/main/kotlin/id/walt/verifier/oidc/VerificationUseCase.kt
Thank for your help!
The text was updated successfully, but these errors were encountered: