How are you calling the encode function? Perhaps simply the order of arguments it wrong?
katafrakt
earthtrip
Yes I just confirmed that I’m passing these into the call correctly
body_hash = encode(payload, client_secret)
encoded_mac_input = encode(mac_input, client_secret)
defp encode(data, key) do
:crypto.mac(:hmac, :sha, key, data) |> Base.encode64()
end
I’m wondering if this is somehow related to the way Jason.encode! turns the struct into a JSON string? One thing I noticed with Jason is it reorders the keys (seems to be alpha ordered??) when you encode a struct. I get that maps aren’t ordered by nature but Poison preserves the order. This shouldn’t matter in the sense that the payload is encoded as part of the signature so the API endpoint shouldn’t care it just struck me as odd.
0
earthtrip
This is partially what’s making testing this difficult if the JSON encoding is somehow done differently then the outputs will always be different even if pass in a static timestamp and nonce
0
earthtrip
Gah! In my testing I modified the sha256 to sha in my encode method. I got it working now.
Sorry and thanks again to everyone!
0
dimitarvp
That could do it, having in mind that :sha corresponds to SHA-1 (160 bit, not 256), if I remember correctly.
0