This support forum is no longer in use. Please use the Cloudinary Community at https://community.cloudinary.com/ to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

Confusion on Signed Parameters

Follow
Avatar
Drew Varner

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

Comments

1 comment

Sort by Date Votes
  • Avatar
    Itay Taragano

    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
    Comment actions Permalink

Post is closed for comments.