-
-
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
Add Security Check page #1665
Comments
I'm happy to work on this if no one is working on it! |
That's great! This would significantly improve accessibility to the security state of Parse Server. Since this requires creating a new page, if you want to get feedback or brainstorm about the new page layout, please feel free to post a wireframe draft. This way we can mitigate any layout changes later on. |
Ok, no worries. Will post here! |
Was hoping to have this for V5 Parse Server but have been a little busy |
We already have the log output of Security Checks on the server side in v5, so that is already a big step forward. |
Haven't had the time for this unfortunately, so if anyone wants it, go for it! |
🎉 This change has been released in version 5.2.0-alpha.28 |
🎉 This change has been released in version 5.3.0-beta.1 |
🎉 This change has been released in version 5.3.0-alpha.1 |
🎉 This change has been released in version 5.3.0 |
New Feature / Enhancement Checklist
Current Limitation
The new Security Check feature of Parse Server currently writes weak security settings in the logs or returns them as JSON via REST request to
/security
endpoint.Feature / Enhancement Description
Add a Security Check page to Parse Dashboard that displays the report in a convenient UI.
The feature would send a request to the
/security
endpoint to receive the report in JSON format. The report schema is already described in parse-community/parse-server#7247 (comment). The page would display a table of that report, ideally with visual elements to highlight failed / successful security checks.Example Use Case
(none)
Alternatives / Workarounds
Read reports in logs or manually via REST request.
3rd Party References
(none)
The text was updated successfully, but these errors were encountered: