parse-community / parse-community/parse-server
Facebook auth adapter can accept invalid configuration
Open
Nobody has claimed this yet.
type:feature
- 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
If a facebook auth adapter is set up with invalid options, it does not log until a user attempts to call the adapter.
Feature / Enhancement Description
The adapter should throw on server start
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 locating the Facebook auth adapter configuration path and the server startup entry point. Trace when invalid options are currently checked, then verify that invalid configuration fails during startup rather than only when the adapter is called.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100