The Back-office Access Restriction module allows to deny access to specific administration pages even for users with permission to access them. This module is intended to be installed on production sites so that some sensitive pages can no more be accessed. Such pages could be:
- Extend
- Extend > Uninstall
- People > Permissions
This module has no configuration page. And it should not! It is intended for developers that will need to edit their services.yml file.
By default the Extend page will return a 403 response but you can define any other specific route by providing the backoffice_access_restriction.routes service parameter in the sites/default/services.yml file.
Example:
parameters:
backoffice_access_restriction.routes:
- system.modules_list
- system.modules_uninstall
- user.admin_permissionsBack-office Access Restriction
git clone --branch 8.x-1.x https://git.drupal.org/project/back_office_access_restriction.git
cd back_office_access_restrictionI'm also a maintainer of the Admin Toolbar module.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | coding_standard_errors-2954990-3.txt | 853 bytes | Deepthi kumari |
| #3 | fixed_coding_standard_errors-2954990-3.patch | 996 bytes | Deepthi kumari |
Comments
Comment #2
romainj commentedComment #3
Deepthi kumari commentedHi,
Fixed Coding Standard Errors. Applied the patch,needs review.
Comment #4
altagrade commentedI see the following error on https://pareview.sh/pareview/https-git.drupal.org-project-back_office_ac...
Comment #5
romainj commented@Deepthi kumari Thanks for the patch.
Comment #6
romainj commentedComment #7
elc commentedI believe this issue should be on Needs Review until the project has been reviewed, or this process will not proceed at all. The reviewer will set it to either Needs Work or RTBC.
Comment #8
romainj commentedComment #9
avpadernoComment #10
sleitner commentedAutomated Review
Review of the 8.x-1.x branch (commit 427fc6a):
This automated report was generated with PAReview.sh, your friendly project application review script.
Manual Review
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.
This review uses the Project Application Review Template.
Comment #11
romainj commented@sleitner that's ok. I changed the README.txt file accordingly.
Comment #12
sleitner commentedComment #13
avpadernoThank you for your contribution!
I am going to update your account so you can opt into security advisory coverage now.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.