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
I recently ran into a canonicalization issue with the RsaSignature2018 suite.
I am using this library through verifiable-credentials-java for the java backend. On the other side, we are using digitalcredentials/vc for the react native application.
The canonicalization of the proof is different in both libraries.
I wanted to know what kind of workaround is being used in this Java library to bypass this bug (so I can also use it in JS), and if it is the expected thing to do. Which one is the solution that would guarantee more interoperability?
Thanks a lot!
The text was updated successfully, but these errors were encountered:
fabrii
changed the title
RSA Canonicalization question
RSA Canonicalization
Jun 7, 2023
I found this workaround w3c/vc-data-model#884 (comment), but I dont know if is is possible to define a context like that with verifiable-credentials-java
Hi!
I recently ran into a canonicalization issue with the RsaSignature2018 suite.
I am using this library through verifiable-credentials-java for the java backend. On the other side, we are using digitalcredentials/vc for the react native application.
The canonicalization of the proof is different in both libraries.
Javascript:
Java:
I opened an issue digitalbazaar/jsonld.js#524 and found out it is related to a problem with the spec.
I wanted to know what kind of workaround is being used in this Java library to bypass this bug (so I can also use it in JS), and if it is the expected thing to do. Which one is the solution that would guarantee more interoperability?
Thanks a lot!
The text was updated successfully, but these errors were encountered: