Conversation
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
1 similar comment
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as resolved.
This comment was marked as resolved.
|
@cla-bot check |
735beb2 to
cdef4c4
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Al2Klimov
left a comment
There was a problem hiding this comment.
13 review comments should be enough for a Friday 13th. :D
| $useCustomCsp = $this->getPopulatedValue('use_custom_csp', 'n') === 'y'; | ||
| if ($useCustomCsp) { | ||
| $this->addHtml((new Callout( | ||
| CalloutType::Warning, |
There was a problem hiding this comment.
- Get Introduce Callout ipl-web#358 done before merging this PR
There was a problem hiding this comment.
Already listed as a requirement
| use ipl\Web\Compat\CompatForm; | ||
| use ipl\Web\Widget\Callout; | ||
|
|
||
| class CspConfigForm extends CompatForm |
There was a problem hiding this comment.
This currently doesn't output the config.ini to the screen like the old ConfigForm did.
I think changing the form type to a CompatForm is still the right call, because we don't want to rely on Zend_Forms forever.
If this behavior essential, we should reimplement the behavior of ConfigFrom as a CompatForm instead.
There was a problem hiding this comment.
Even in new modules we reimplemented this behavior: Icinga/icingadb-web#1269
So I'd not downgrade this functionality.
| ); | ||
|
|
||
| $this->addPolicyTable( | ||
| t('Dashboard'), |
There was a problem hiding this comment.
If you're concerned about #5477 (comment), you should be about this one too:
As not a IW2 dev, I'd have absolutely no clue that these are only my dashboards (if any!) and others may have their own.
Consider listing the dashboard-CSPs of all users, after all we have them (by name) in the preference store or something idk.
Module-provided dashboards should already be included as you should see all modules as admin. I guess they may contain external URLs as well.
There was a problem hiding this comment.
I'm not sure if we always have access to all users in something like LDAP.
Also listing all dashboards and menu entries for all users in an organization on every initial request seems pretty expensive.
If a module wants something whitelisted beyond what is automatically detected, it can already do that.
There was a problem hiding this comment.
We always have access to all users' dashboards and menu entries.
Imagine you make a custom CSP based on the generated one, but latter misses non-your dashboards.
f9f19b4 to
3a4e7ac
Compare
- Reload of form change if Csp was previously enabled in `ConfigController` - Use default attributes in `CspConfigurationTable` - Rename `$policyDirectives` to `$directivePolicies` in `Csp`
This tab requires the new config/security permission
This allows for checkboxes integrated inside the table. This commit also adds disabling modules, dashboards and navigation items individualy.
3a24ab1 to
bfec859
Compare







Taking over #5337 (#5337 (comment)) and implementing an override for a completely custom CSP-Header.
As well as adding a table below the form which displays the source of the automatically generated CSP-Header.
Styling for this table is still WIP.
requires Icinga/ipl-web#358
requires Icinga/ipl-web#361
closes #5337
closes #5333