Development and Administration Tools

Development and Administration Tools

Notifications

To configure the email notification read the documentation for email notification (wiki).

For temp configuration or tests i recommend to use command line arguments (wiki).

Debug the Content Security Policy

To debug the CSP you may use the --security arguments (i should not change the security configuration for security reason) and configure the email notification. You have a application/json page on http(s)://<server>:<port>/csp/debug/ with the Content Security Policy Report

WebScripts --security --admin-adresses "admin@email.com" --n-adr "notification@email.com" --s-server "smtp.email.com"

Tests

Unittest

python -m unittest discover -s test -p Test*.py -v

File	Statements	missing	coverage
WebScripts.py	759	3	99%
commons.py	399	2	99%
utils.py	332	6	98%
Errors.py	27	0	100%

Hardening audit

1. To harden the WebScripts installation: run the installation command with privileges using these arguments: --admin-password=\-p and --owner=\-o. See the examples on installation page and deployment page.
2. The hardening audit is performed when WebScripts server starts. The audit report is written in audit.html, audit.json and audit.txt and emailed to Administrators. HTML report examples:
   • Windows
   • Linux
   • docker with Apache and mod_wsgi HTML report
   • docker with Nginx as HTTPS proxy HTML report
   • docker HTML report

Functional tests and WebScripts pentest tool

Functional tests and WebScripts pentest tool.

Test configurations and interface

To test the interface and configurations, I added a python script, invisible in the web index page, but you can use it to try, test or discover new features. The script is called test_config.py, you can get it from this URL (on localhost:8000) http://127.0.0.1:8000/web/scripts/test_config.py.