My understanding is that if I write any record including the string {AES128_CMAC_SIGNATURE_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX} when I read it, it will magically show the salted signature, correct?
I tried on my apex, but when I read my new record with TagInfo I still see the long series of X, no magic signature. I guess this means I have an older version of the applet? Or I misunderstood the workflow?
This URL will take the signature received and use our test API key with the API to obtain validated unsigned JSON from /validate.json (so it’s readable). If you prefer the signed JWT just use /validate in your own solution.