Managing external identities to enable secure access for partners, customers, and other non-employees
Could you confirm if the P2 license is still valid and not expired?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Good afternoon. We've been working with Verifiable Credentials (preview) for 1.5-2 months. We've started with Microsoft's reference issuer/app.js and verifier/app.js code (found here https://github.com/Azure-Samples/active-directory-verifiable-credentials) and have made some modifications in order to issue & verify VCs using our own key vaults, DiDs, etc. Yesterday after deploying an updated VC and updating our issuer/app.js code I started seeing this error (contract and tenant id are not actual ones) :
{
"error": {
"code": "DependencyFailure",
"message": "Failed to obtain contract 'XYZContract' for tenant '12345678-1234-1234-1234-1234567890ab'."
}
}
Has anyone encountered this before?
Managing external identities to enable secure access for partners, customers, and other non-employees
Could you confirm if the P2 license is still valid and not expired?
Does your account and the Verifiable Credential Issuing service SPN have "Storage Blob Data Reader" permission on the container? Could you check that as the first step. Here is the section in the document that explains the permissions required
https://learn.microsoft.com/en-us/azure/active-directory/verifiable-credentials/enable-your-tenant-verifiable-credentials#assign-a-blob-role
Also, does your tenant have Azure AD Premium P2 License?