-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add dashboard option allowAnonymousUser
#2066
base: alpha
Are you sure you want to change the base?
Conversation
Thanks for opening this pull request!
|
Still some checks failing. Please request another review once this is ready. |
Is this a breaking change? Does an existing deployment need a reconfiguration to maintain the same security? |
I would say so, an existing localhost configuration would need to be changed but remote servers should function the same as before |
I guess our deprecation policy should be (or is in practice already) extending to Parse Dashboard. So breaking changes should probably happen accumulated once a year only as well. Otherwise we may have a breaking change every other month. Is there a way to make this non-breaking? For example, if the new option is not set, fall back to the old behavior. |
The only way I think is if we set |
Yes, I think we should avoid that |
Could you rebase this on alpha? |
## [4.1.1-alpha.1](parse-community/parse-dashboard@4.1.0...4.1.1-alpha.1) (2022-04-04) ### Bug Fixes * security upgrade js-beautify from 1.14.0 to 1.14.1 ([parse-community#2077](parse-community#2077)) ([e4ea787](parse-community@e4ea787)) * security vulnerability bump minimist from 1.2.5 to 1.2.6 ([parse-community#2070](parse-community#2070)) ([3d0407e](parse-community@3d0407e))
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
# [4.0.0-alpha.17](parse-community/parse-dashboard@4.0.0-alpha.16...4.0.0-alpha.17) (2022-02-23) ### Bug Fixes * security upgrade prismjs from 1.26.0 to 1.27.0 ([parse-community#2047](parse-community#2047)) ([3afb24e](parse-community@3afb24e))
Snyk has created this PR to upgrade @babel/runtime from 7.17.0 to 7.17.2. See this package in npm: https://www.npmjs.com/package/@babel/runtime See this project in Snyk: https://app.snyk.io/org/acinader/project/3e039b91-2450-4b56-8420-baf56cab388e?utm_source=github&utm_medium=referral&page=upgrade-pr
# [4.0.0-alpha.18](parse-community/parse-dashboard@4.0.0-alpha.17...4.0.0-alpha.18) (2022-03-02) ### Bug Fixes * upgrade @babel/runtime from 7.17.0 to 7.17.2 ([parse-community#2055](parse-community#2055)) ([93335e9](parse-community@93335e9))
Snyk has created this PR to upgrade express from 4.17.2 to 4.17.3. See this package in npm: https://www.npmjs.com/package/express See this project in Snyk: https://app.snyk.io/org/acinader/project/3e039b91-2450-4b56-8420-baf56cab388e?utm_source=github&utm_medium=referral&page=upgrade-pr Co-authored-by: Manuel <5673677+mtrezza@users.noreply.github.com>
# [4.0.0-alpha.19](parse-community/parse-dashboard@4.0.0-alpha.18...4.0.0-alpha.19) (2022-03-10) ### Bug Fixes * upgrade express from 4.17.2 to 4.17.3 ([parse-community#2058](parse-community#2058)) ([f8dc602](parse-community@f8dc602))
# [4.0.0-alpha.20](parse-community/parse-dashboard@4.0.0-alpha.19...4.0.0-alpha.20) (2022-03-16) ### Features * change string filter description ([parse-community#2059](parse-community#2059)) ([bb1e184](parse-community@bb1e184))
Snyk has created this PR to upgrade otpauth from 7.0.10 to 7.0.11. See this package in npm: https://www.npmjs.com/package/otpauth See this project in Snyk: https://app.snyk.io/org/acinader/project/3e039b91-2450-4b56-8420-baf56cab388e?utm_source=github&utm_medium=referral&page=upgrade-pr
# [4.0.0-alpha.21](parse-community/parse-dashboard@4.0.0-alpha.20...4.0.0-alpha.21) (2022-03-18) ### Bug Fixes * upgrade otpauth from 7.0.10 to 7.0.11 ([parse-community#2061](parse-community#2061)) ([c379306](parse-community@c379306))
6921339
to
b9cc888
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems the discussion got stuck at how to avoid making this a breaking change. Once this has been figured out please request another review.
d32a043
to
0f42a34
Compare
New Pull Request Checklist
Issue Description
Parse Dashboard assumes security if it detects a remote server, which is unreliable. This adds the option
allowAnonymousUser
which defaults to false.Related issue: #2065
Approach
allowAnonymousUser
that defaults to false. Setting this to true allows Dashboard to run with no users.This also add additional security for when dashboard is run on localhost with no options. Previously Dashboard was effectively assuming the
dev
parameter if localhost. This PR will only run Dashboard indev
mode if it's implicitly set. To get previous localhost behaviour, thedev
parameter is required to be set.TODOs before merging