parse-community / parse-community/parse-server
Auth adapter error codes should be specific
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Currently, if an additional adapter is used, and login is attempted without additional data is thrown, error code -1 is thrown. Also, if there is a throw from within validateLogin, the error code is 141.
Feature / Enhancement Description
The error codes for each of these cases should be specific, so UI can update to allow users to provide additional auth data.
Example Use Case
Alternatives / Workarounds
3rd Party References
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 tracing the additional adapter login path and the validateLogin error handling described in the issue. Review existing authentication error-code conventions and determine how the two cases should be distinguished; done means each case exposes a specific code that lets the UI request additional authentication data when appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100