Confusion on Signed Parameters

Drew Varner

October 29, 2014 17:22

I am developing Cloudinary API for Erlang. I am implementing the authentication method described here:

http://cloudinary.com/documentation/upload_images#request_authentication

As such, I only include the following parameters in my signature:

callback, eager, format, public_id, tags, timestamp, transformation, type

However, I receive the following error response (HTTP status code 401) when constructing a signed upload request:

"Invalid Signature a9687302e8568dbc8ca3794d4c9c493233ab74e2. String to sign - 'public_id=foo1&timestamp=1414602730&unique_filename=false'."

According to documentation on manually signing a request, the unique_filename parameter is not a parameter that should be used in a signature calculation.

 

0

• 

  Itay Taragano

  November 02, 2014 10:57

  Hi Drew,

  You're correct, I'm sorry for the confusion. Our documentations will be updated shortly to better explain this, thank you for pointing that out.

  Actually, all parameters should be included in the signature except the  api_key .  So in the case you shared, you should indeed sign the  public_id ,  timestamp  and  unique_filename  parameters.

  0

Post is closed for comments.