JolocomLib.util.validateDigestable fails with '@context must be an object.'

[palinka]

Describe the bug Although following https://jolocom-lib.readthedocs.io/en/latest/, JolocomLib.util.validateDigestable fails with above error.

I had the impression this did not happen before 19th of March, but can be reproduced 100% since then. Need to check eventual external dependencies for context..

Here more infos:

identityWallet.create.signedCredential returns an array for the context:

JolocomLib.parse.signedCredential return undefined as consequence for above:

To Reproduce I implemented a self-contained unit-test here.

Use yarn testSignatureValidation to execute.

Expected behavior A credential can be signed by JolocomLib.

TODO

• Downgrade json-ld for an A/B test
• It may be the case the DID spec is not complaint with the json-ld spec.

[palinka]

json-ld was updated here: https://github.com/jolocom/jolocom-lib/commit/025364e73b43e21827ec1a9ebe2c1ab0243af75f

Maybe this is connected and did not bubble up, because

• Neither unit- nor integration tests of the lib catch the bug.
• Backends do sign, but are not yet updated to jolocom-lib 2.3.0.
• The SmartWallet does not sign.

Maybe json-ld did not catch the undefined context in previous version.

[chunningham]

The JSON-LD spec does not specify what type the @context block should be and the VC spec has an example with an array. The JSON-LD library is not processing the context field properly I suspect.

[Exulansis]

Does this still need to be addressed? Otherwise I can close this.

[Exulansis]

@chunningham @mnzaki @VolkerSchiewe I am closing this issue for now, if this reoccurs in some way, this can be reopened.