"Credential not found" error on Authenticator app when trying to verify the issued credential

Question

I've been following the latest Azure AD Verifiable Credentials tutorial (ver. June 18th 2022) and all have been well until I want to verify the issued credential.

in sample web application's config.json, "azCertificateName" and "CredentialManifest" match the credential I want to verify.
Since I'm both issuer and verifier, I allocate the same DID to "IssuerAuthority" and "VerifierAuthority" but still could not request the credential.

Please let me know if my configuration is wrong/insufficient or if I should modify sample application's code. Thank you in advance!

Answer 1

I faced a similar issue. In my case I had defined the VC with a custom name (ZanzibarVerifiedCredentials) than what was expected in the Sample

Double check the credential type name you used in when creating the Verifiable Credential from the Azure portal and the one requested by the sample (this is defined in presentation_request_config.json)

In my case, I defined my credential name as ZanzibarVerifiedCredentials so had to change the presentation_request_config.json as below.

{
"authority": "did:ion: THIS IS YOUR DID FROM THE VC PAGE IN AZURE PORTAL ...set at runtime...",
"includeQRCode": false,
"registration": {
"clientName": "Verifiable Credential Expert Sample",
"purpose": "the purpose why the verifier asks for one or more VCs"
},
"callback": {
"url": "...set at runtime...",
"state": "...set at runtime...",
"headers": {
"api-key": "OPTIONAL API-KEY for VERIFIER CALLBACK API"
}
},
"presentation": {
"includeReceipt": true,
"requestedCredentials": [
{
"type": "ZanzibarVerifiedCredentials",
"purpose": "the purpose why the verifier asks for a VC",
"acceptedIssuers": [ "...set at runtime..." ]
}
]
}
}

If the names are the same then it's a different case than mine.