Handle auth errors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Authentication errors (regardless if just temporary or long-term) should be handled both on the server-side by catching and handling horde exceptions and on the client-side by showing better error messages for this type of error and suggesting to change the password.
TODO
- More exception handling on the server-side
- Auth exception detection and special handling
- Definition of a auth error response (status code + messages)
- Error detection on the client-side
- Better error messages on the client-side
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
No files, tests, or entry points are named. Start by locating the server-side Horde exception handling and the client-side authentication error handling, then define the response status and messages before tracing how each side detects and presents auth failures. Done means temporary and long-term authentication errors are handled on both sides with clearer messages and password-change guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- authentication, backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100