silverstripe/silverstripe-securityreport

"Users, Groups and Permissions" report in Silverstripe CMS

Security Report

This module adds a "Users, Groups and Permissions" report in the CMS, so that an administrator can get a quick overview of who has access to the CMS.

Installation

composer require silverstripe/securityreport

Subsites Support

If the Subsites module is installed then an additional column will be added, allowing you to see which subsites this user can edit pages on.

To edit the permission to check for when filtering these subsites, you can update the Member.subsite_description_permission config to any other permission. By default this is set to SITETREE_EDIT_ALL.

silverstripe-securityreport's Issues

Permissions report column for subsites is at the start instead of the end

Version: CWP 2.2.x-dev

It should be at the RHS end not the LHS

Fix travis builds for master branch

Add new Travis configuration (see blog, etc for examples).

Missing columns in report

The security report no longer contains the columns showing the date and time of the last visit. Were these intentionally removed?

This affects:

silverstripe/securityreport               dev-master 24a71d6

silverstripe/framework                    4.1.x-dev 9ed3cd4
silverstripe/cms                          4.1.x-dev 7dea009
silverstripe/reports                      4.1.x-dev ac23686

Compare against e.g.:

silverstripe/securityreport               1.0.10 

silverstripe/framework                    3.6.5   
silverstripe/cms                          3.6.5 

Move Scrutinizer repo to SS

Hey again @dhensby - this one too if you don't mind https://scrutinizer-ci.com/g/silverstripe-labs/silverstripe-securityreport/

UX Overflow content hidden if screen width too narrow

When opening the security report (through the CMS' Reports navigation) on a window/tab with narrow screen width, the overflow content is hidden and can not be accessed by other means than extending the screen width.

silverstripe/securityreport               dev-master 24a71d6

silverstripe/framework                    4.1.x-dev 9ed3cd4
silverstripe/cms                          4.1.x-dev 7dea009
silverstripe/reports                      4.1.x-dev ac23686

Note that in contrast in CWP 1.8.1 a horizontal scroll bar gets added, so the relevant content is still accessible.

Array to string conversion in CSV report

For reference, this extension replicates framework code that has a bug as described in issue #6617 and fixed in PR #6622.

When I get the chance I'll put in a PR for the fix, hopefully today.

Regression with subsites compatibility

There's a test failing against the latest subsites version: https://travis-ci.org/silverstripe/cwp-recipe-kitchen-sink/jobs/423801729#L950

This would've been caused by silverstripe/silverstripe-subsites#388

Needs investigation. We should start by separating that test into individual cases to ensure it's not pollution of the global state between loading each fixture and running tests on them

TODO: Update Unit tests. Pre-fill the report with fixture-defined users.

Description

Update UserSecurityReportTest::setUp() to support pre-filling the report with fixture-defined users.

See:

silverstripe-securityreport/tests/php/UserSecurityReportTest.php

Line 45 in de1a170

* @todo pre-fill the report with fixture-defined users

Report title should be underneath actions toolbar

SS 4.1.x-dev, CWP 2.0.x-dev, securityreport 2.0.0

As per silverstripe/silverstripe-reports#100, the actions toolbar should be at the top of the report with content appearing underneath it rather than above it.

cc @clarkepaul

Check and update module for SS4 compatibility where necessary

Acceptance Criteria

• Module works on SS4
• Beta tag released

Pull requests

• #28
• #29

Add support for PostgreSQL

At the moment some of the code is incompatible with PostgreSQL. Since it's a supported database driver in SilverStripe, we should add support for it.

Some example issues from Travis builds:

1) SilverStripe\SecurityReport\Tests\UserSecurityReportTest::testSourceRecords
SilverStripe\ORM\Connect\DatabaseException: Couldn't run query:
UPDATE "Member"
 SET "ClassName" = $1, "Locale" = $2, "FirstName" = $3, "Surname" = $4, "Email" = $5, "Created" = $6, "LastEdited" = $7
WHERE ("ID" = $8)
ERROR:  invalid input syntax for type timestamp: "1393319440"
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/Connect/DBConnector.php:64
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/postgresql/code/PostgreSQLConnector.php:234
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/Connect/Database.php:168
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/Connect/Database.php:222
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/Connect/Database.php:170
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/DB.php:445
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/Queries/SQLExpression.php:115
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/Connect/Database.php:348
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/DB.php:493
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/DataObject.php:1318
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/ORM/DataObject.php:1364
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/Dev/FixtureBlueprint.php:146
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/Dev/FixtureFactory.php:85
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/Dev/YamlFixture.php:154
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/framework/src/Dev/SapphireTest.php:278
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/silverstripe/securityreport/tests/UserSecurityReportTest.php:46
/home/travis/build/creative-commoners/recipe-reporting-tools/vendor/phpunit/phpunit/phpunit:52

TODO: Investigate should GridFieldComponents change behaviour based on whether others are available in the config

Description

GridFieldExportReportButton::generateExportFileData(): Investigate should GridFieldComponents change behaviour based on whether others are available in the config.
See:

silverstripe-securityreport/src/Forms/GridFieldExportReportButton.php

Line 63 in de1a170

// @todo should GridFieldComponents change behaviour based on whether others are available in the config?