Setting URLConfig.signUrl doesn't actually sign the URL

[jonasb]

From what I can see setting signUrl on URL config doesn't have any effect. It seems like I need calculate the signature myself.

Am I missing something?

[Vdeub-cloudinary]

@jonasb - the signURL parameter is only relevant for backend SDKs, if you use frontend SDKs you will effectively need to calculate the signature and use the .setSignature("signature") method to sign your URL. That's why you only see this parameter documented under backend SDKs cf here.

[patrick-tolosa]

@jonasb as mentioned, this SDK is currently client-side only, we plan to add some server-side functionality (such as URL signatures) in the near future.

I'm closing this issue for now, but please reply if needed.

[jonasb]

Ah, ok. It wasn't clear to me that this library is frontend only for now. Thanks for letting me know!

[patrick-tolosa]

We'll update once the needed adjustments are needed for server-side support.

[mikestopcontinues]

Hey, what's the status on adding signing?

[mikestopcontinues]

Just to follow up: The library makes it more difficult than normal to sign the request because it conceals the transformations that would otherwise need to be sorted, serialized, and signed. It would be great to have something like:

image.setSignature((payload) => string);

Or perhaps even:

new Cloudinary().setHasher((string) => string);

In the latter case, the library could manage which URLs needed to be signed (either by config or by .sign())... which I suspect is what most users would expect. Thoughts?

[PixelCook]

@mikestopcontinues thanks for the feedback, this fix is currently still slotted for development. I don't currently have an ETA but I'll double-check with the team for an update.

[mikestopcontinues]

@PixelCook Any update on the ETA?

[PixelCook]

@mikestopcontinues Currently I do not have a date yet, but it is still slotted for development.