Configure node to generate hash of certificate file

I am having difficulty generating the correct hash of a file and need assistance finding and fixing my mistake in the configuration of the hash node.

The file is https://files.onlosant.com/622a42d69ac44edc3def2017/rootCertificates/losant_aws.pem.

The hash in Losant is “77c22b27e8af4a5fbb2b078a2c2135bf2507ba6748114a6463526e8b7671ac8c”, but the expected value is “50622f72c5232843277158d1976a964b9342125755c93451584f2aea11b9f997”(SHA256 - Online Tools). The hash generated by github.io also matches what the embedded device generates using Mbed TLS sha256.

Just to confirm, you want to generate a hash of the file contents, and not the file URL? Because in that screenshot you are generating a hash of the characters https://files.onlosant.com/622a42d69ac44edc3def2017/rootCertificates/losant_aws.pem.

You will need to download the contents of the file first using an HTTP Node, store the result on the payload at a payload path, and then reference that contents using a string template pointing to the location of the file content.

Thanks. I’ll try that.