Improve permission denied error messages to specify client vs user
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Currently, when the user performs an unauthorized action, they receive a message such as the following:
ERROR: Server responded with error 403 "Forbidden"
ERROR: Error Body: {"error":["missing read permission"]}
While this is clear enough in many cases, it could be improve by:
-
Specifying the identity of the actor in question. "missing read permission for client[NAME]" or "missing read permission for user[NAME]". This will help users who might have a client and user with the same name and are accidentally using the client rather than the user.
-
Specifying the object that they don't have permission on.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Erlang code that formats 403 permission errors and inspect any existing tests for those messages. Done means the error identifies whether the missing permission belongs to a client or user and names the object involved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100