Please clarify Cloudinary account vs decap user

[tpluscode]

The docs says

To use this library or use the restricted Cloudinary API endpoints, the user must have access to the Cloudinary account login details or the api_secret associated with the cloud_name and api_key.

What does it mean exactly? That all users need to have cloudinary access, else they would not have the ability to upload media?

[martinjagodic]

The user needs both an account to access the CMS, and a separate account to access Cloudinary. As a developer, you need to add cloud_name and api_key to the config. Usually users have to log in to cloudinary in a separate tab - The login prompt in the Decap widget is not reliable.

example:

media_library:
  name: cloudinary
  config:
    cloud_name: test_name
    api_key: 1234567890

[tpluscode]

Hm, this is a little awkward to require that content editors need to also manage cloudinary credentials and log in.

What would it take to implement a cludinary proxy which we'd authenticate using the decap token? Does that make sense?

[martinjagodic]

I agree, but this is a limitation of the Cloudinary widget. I'm not sure how this would work, since Decap doesn't handle auth, your chosen backend does.