Added security check report settings and templating
This commit is contained in:
@@ -36,15 +36,19 @@ lib/Module/Security/
|
||||
SecurityBcSettingsGateway.php — global BC connection settings (core settings table, encrypted)
|
||||
SecurityOAuthTokenService.php — OAuth2 token acquire + encrypted cache
|
||||
SecurityBcGateway.php — thin BC OData (ONLY customer-search + domains-for-customer)
|
||||
SecurityReportPdfService.php — customer PDF report (Dompdf); pure context builder + render
|
||||
SecurityReportPdfService.php — customer PDF report (Dompdf); picks custom template or built-in PHTML default
|
||||
SecurityReportSettingsGateway.php— report HTML/CSS template (core settings table, clear text)
|
||||
SecurityReportTemplateService.php— {{var}} substitution into the admin template + default scaffold (pure)
|
||||
SecurityReportLogoService.php — report logo upload/serve (storage/security/report-logo, ImageUploadTrait)
|
||||
pages/security/ — actions (*.php) + views (*.phtml)
|
||||
checks/report($id).php — streams the customer report PDF (gated on steps 1–5 complete)
|
||||
report-design/ — report look config: logo upload + HTML/CSS template editor; logo-file() serves the logo (settings.manage)
|
||||
templates/aside-security-panel.phtml— sidebar navigation
|
||||
templates/pdf/customer-report.phtml — customer report PDF template (hydrated by SecurityReportPdfService)
|
||||
templates/pdf/customer-report.phtml — built-in default report layout (used when no custom template is stored)
|
||||
i18n/default_de.json + default_en.json — keep both in sync (identical key sets)
|
||||
migrations/ — 003 SQL files (module:migrate)
|
||||
web/css/security.css | web/js/ — module styles + runtime components + page scripts
|
||||
tests/Module/Security/Service/ — 7 test files (happy path + edge case)
|
||||
tests/Module/Security/Service/ — 10 test files (happy path + edge case)
|
||||
```
|
||||
|
||||
---
|
||||
@@ -87,9 +91,13 @@ template edits never mutate in-flight checks. JSON state shapes:
|
||||
Main menu entry via the `aside.tab_panel` slot (icon `bi-shield-check`, permission `security.access`).
|
||||
Pages: `security/checks` (list), `security/checks/create` (wizard), `security/checks/edit/{id}`
|
||||
(workspace), `security/checks/report/{id}` (streams the customer PDF report),
|
||||
`security/templates` (+create/edit/{id}), `security/settings`, plus data endpoints
|
||||
`security/templates` (+create/edit/{id}), `security/settings`, `security/report-design`
|
||||
(customer report look: logo + HTML/CSS template), plus data endpoints
|
||||
`security/checks-data`, `security/templates-data`, `security/customer-search-data`,
|
||||
`security/customer-domains-data`, `security/settings/test-connection-data`.
|
||||
`security/customer-domains-data`, `security/settings/test-connection-data`,
|
||||
`security/report-design/logo-file` (serves the uploaded report logo).
|
||||
|
||||
`report-design` reuses the `security.settings.manage` permission (no new permission key).
|
||||
|
||||
## JS runtime components
|
||||
|
||||
|
||||
Reference in New Issue
Block a user