How to handle API Keys

Open
#713 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, nodejs

Research direction

Start with the issue's question about exposing a Cloudinary API key while keeping the secret protected. Establish the project's intended guidance for returning and using the key, then document a clear, security-reviewed answer; the payload names no files or tests to run.

Written by the indexing model from the issue text.

Description

Is it safe to disclose my API Key (not the secret) to the users of my app? For example returning it in the body of a response to later use it to upload signed files?

Dominant language
JavaScript
Stars
672
Forks
318
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudinary/cloudinary_npm

All issues in cloudinary/cloudinary_npm

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.