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
the VC/VP Data Integrity specification requires in numerous places, that two URIs be the same, for example the issuer and the verificationMethod contained in the proof object. These items typically are URIs.
Normally, the issuer would contain the general resource identifier, e.g. did:web:the-issuer, while the verification method would contain a URI fragment, indicating the key material used to create the proof, e.g. did:web:the-issuer#signing-key-1.
Using the JDKs URI#equals method will always fail in those cases, because it will include the fragment.
Thus, we need our use-case specific URI comparison.
Which Areas Would Be Affected?
VC/VP verification
Why Is the Feature Desired?
Compliance with the spec.
Solution Proposal
convert the URIs to a string, chop off the fragment, perform string equals comparison.
The text was updated successfully, but these errors were encountered:
Feature Request
the VC/VP Data Integrity specification requires in numerous places, that two URIs be the same, for example the
issuer
and theverificationMethod
contained in the proof object. These items typically are URIs.Normally, the issuer would contain the general resource identifier, e.g.
did:web:the-issuer
, while the verification method would contain a URI fragment, indicating the key material used to create the proof, e.g.did:web:the-issuer#signing-key-1
.Using the JDKs
URI#equals
method will always fail in those cases, because it will include the fragment.Thus, we need our use-case specific URI comparison.
Which Areas Would Be Affected?
VC/VP verification
Why Is the Feature Desired?
Compliance with the spec.
Solution Proposal
convert the URIs to a string, chop off the fragment, perform string equals comparison.
The text was updated successfully, but these errors were encountered: