You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
After we update to the latest VC2 libs, VCs that don't have a uri value for their top level id will no longer verify.
Describe the solution you'd like
Add a check on the id and if it isn't a uri then display a message:
"The id of a verifiable credential must be a URI. Your credential's id is not a URI and may therefore have been issued as part of an early test pilot program. Please ask your issuer for a replacement if needed."
Describe alternatives you've considered
Could try to provide backward compatibility by modifying or working around the VC libs , but given that credentials issued thus far are for pilots, the cost of maintaining that backward compatibility is too high.
Is your feature request related to a problem? Please describe.
After we update to the latest VC2 libs, VCs that don't have a uri value for their top level id will no longer verify.
Describe the solution you'd like
Add a check on the id and if it isn't a uri then display a message:
"The id of a verifiable credential must be a URI. Your credential's id is not a URI and may therefore have been issued as part of an early test pilot program. Please ask your issuer for a replacement if needed."
Describe alternatives you've considered
Could try to provide backward compatibility by modifying or working around the VC libs , but given that credentials issued thus far are for pilots, the cost of maintaining that backward compatibility is too high.
Additional Context
Same issue applies to VerifierPlus: digitalcredentials/web-verifier-plus#134
The text was updated successfully, but these errors were encountered: