Issue with Certificate Upload - "Invalid Credential" Error

1

I have used Cert-tools to create unsigned certificates and Cert-issuer (with Ethereum) to generate signed certificates.

However, when I upload the signed certificate to the app, I encounter the following error:
“Invalid Credential”

I would appreciate any guidance on resolving this issue.

Additionally, I would like to know:

  1. How to generate the Issuer URL?
  2. How to generate a one-time code for the certificates?

Thank you for your help!

@lemoustachiste

2

The error should be visible in the browser console.

Your issuer URL should be the URL of your issuer profile. It can be a DID. You can look at a hybrid profile here: https://www.blockcerts.org/samples/3.0/issuer-blockcerts.json

Your issuer profile should reference a public key listed in verificationMethod and available in say assertionMethod.

That same key should be used in the proof.verificationMethod.

That key should be presented in such format (JWK is fine) that the verifier can transform the public key into the issuing address used for the blockchain network of the transaction.

You should host your document somewhere accessible from the web (no CORS).

How to generate a one-time code for the certificates?

I’m not sure what you mean by this.

3

@lemoustachiste

Thanks for the quick response
Regarding the onetime code and issuer url the following forum help me alot

However i just want to know can i verify the certificate which i generated using ethereum in android-wallet and ios-wallet ?

Is ios-wallet accepting V3 certificates ?

4

Yes, both apps are compatible with v3

5

@lemoustachiste
But when i try to validate certificate it works well in site

But when i try to validate the same certificate in the mobile i’m facing an error as show in the image

shared image
shared image1080×2388 107 KB

6

Just to confirm, this is the Android app, latest version?

7

I have replicated the issue, I will take a deeper look at it.

8

Hey,

so I believe I have found the issue.

If you pull up JSON-LD Playground and paste your certificate in, then take a look at the canonized tab, you’ll see a safe mode error, which means that this property didn’t get properly hashed when issuing (last time I checked the pyld library safe mode wasn’t implemented so it’s not failing at issuance time).

You’ll need to define the key college as a jsonld object into your context and issue again.

The fact that it passes on blockcerts.org is more the bug than the other way around so I’m looking into that.