1) You can try using the demo certs on OpenCerts => https://dev.opencerts.io/static/demo/ropsten.opencerts 2) a) For the moment we haven't defined it completely, it's just something we thought about for instance in case people want to share OpenCerts but doesn't want to allow other to keep it b) Please use opencerts.io (or dev.opencerts.io) for OpenCerts document. Tradetrust is meant for eBL (even if OpenCerts will work on it)

Thanks Nebulis. I've tested with the opencerts provided. However, it still showing "false" for summary.all

When I'm testing with the endpoint "https://api-ropsten.opencerts.io/verify", I'm able to get the result "true" for summary.all, as shown in the screenshot attached. Do I need to update any config when hosting the API ?

Hi,

Indeed you need to configure the function => https://github.com/OpenCerts/opencerts-functions/blob/master/src/verify/config.js#L2

The error shows that there is problem with the document status (i.e. issue / revoke), which is likely because the deployed function connect to homestead instead of ropsten.

Try to set NETWORK to "ropsten" and it should work

Thanks Nebulis, it's working after i update it to ropsten.

Cool. I will probably make this a terraform module in 2 weeks. Let me know if you are interested

Got it, thanks Nebulis! I'll need to discuss with my infra team regarding this. Can confirm if your terraform module will host this API in your own server right ? (apologies that I'm not so familiar with how's terraform work)

No, terraform will help you to deploy on your own infrastructure :)

Hi Nebulis, thanks for the offering ! yes, we are interested on that. Please let me know what you need from me in order to create the terraform module =) (and can I know what is the action that terraform module will perform? our infra team need to assess it. Can email me via "[email protected]") Thanks !!

I created this issue to track => https://github.com/OpenCerts/opencerts-functions/issues/58 You can subscribe and you will receive notifications when done

As per the actions performed, it will look like this => https://github.com/Open-Attestation/terraform-aws-status-api One difference that I can think about is that verify API as is doesn't need dynamodb

Great! Thanks Nebulis =)

Thanks Nebulis, ady subscribed to the issue and inform my Infra team. Regarding the “PermittedAction”, is it okay for us to just leave it empty for now? And please let us know if this field become mandatory in the future and the value to put in this field. Thanks Nebulis! =)

Yes ok to leave it empty

Added scripts to help for deployment using sls (and not terraform as proposed initially) => https://docs.opencerts.io/docs/api/verify#deployment

Enquiry on Verify OpenCerts payload Hi Nebulis, Refer to the screenshort below, we would like to know which field is used to indicate whether the OpenCerts is issued by SSG registry Training Providers. Are you supposed to look at “issuerIdentity” = true?

Thanks for the update Nebulis, had inform my team regarding the usage of sls for deployment. I noticed the network setting for production_network to be set to "homestead" instead of "ropsten". As per tested previously, the network had to set to "ropsten" for the API to work, can confirm which setting should be the correct one? And can please help to clarify on HengSiang's question above as well? Thanks !

it depends where you issue your documents but

so If you want to deploy to a test environement you should use ropsten, otherwise you should use homestead