parse-community / parse-community/parse-dashboard
Add Parse Dashboard option `allowAnonymousUser`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
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, Parse Dashboard relies on IP checking to check if a Dashboard is running remotely, and add additional security if so. This is problematic if you are using a proxy, which can result in protections becoming disabled.
Feature / Enhancement Description
Rather than relying on IP checking for security, add Parse Dashboard option allowAnonymousUser. This would also change the behavior of being able to run Parse Dashboard locally without allowInsecureHTTP or dev.
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 existing IP checking and the allowInsecureHTTP and dev options in Parse Dashboard. Define how allowAnonymousUser should control local and remote behavior, including proxied deployments, and verify the resulting security behavior with the relevant existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100