Remove forms that request sensitive information
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- jekyll
- Domain
- documentation
Research direction
Start at the linked “Your configuration” section in the documentation source and locate the form that requests the Parse Server URL, master key, and client keys. Replace the sensitive-information fields with common placeholders and check the surrounding examples to ensure the docs no longer ask users to submit credentials.
Written by the indexing model from the issue text.
Description
Link to section:
https://docs.parseplatform.org/rest/guide/#your-configuration
What is the issue?
I think this is a well-intended feature, but I don't think we should provide it for security reasons.
This feature asks developers to enter their Parse Server URL, master key and client keys on a webform and submit it. Asking that of a developer goes against establishing awareness for good security practice and facilitates phishing. IMO we should never ask a developer to enter this information anywhere, but in fact create awareness about the sensitivity of that data and remind to never share it with anyone outside a project.
The only way such a feature may make sense was if the docs were made part of a Parse Dashboard backend where the user logged into the dashboard already has access to that information and it is merely displayed from the backend data.
Can you propose a solution?
I'm for removing this feature from the docs and just use common placeholders throughout the code.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 506
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from parse-community/docs
-
📙Opendocs:cloud-code type:docs
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
parse-community/docs#936 ·
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
parse-community/docs#889 · 7 comments ·
-
docs:sdk-js
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
parse-community/docs#961 ·
-
type:bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
parse-community/docs#950 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
parse-community/docs#947 ·
All issues in parse-community/docs
Similar issues
-
area:docs area:render bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
registrystack/registry-stack#1618 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3897 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
siderolabs/docs#791 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nestjs/docs.nestjs.com#3554 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 98/100
huggingface/course#1320 ·
Maintainers usually reply within 1 day