nepada/security-annotations

Security annotations for Nette presenters and components.

Security Annotations

, _(*1)

Installation

Via Composer:, _(*2)

$ composer require nepada/security-annotations

Register the extension in config.neon:, _(*3)

extensions:
    securityAnnotations: Nepada\Bridges\SecurityAnnotationsDI\SecurityAnnotationsExtension

Usage

This package builds on top of the standard access authorization of Nette components, namely Nette\Application\UI\Component::checkRequirements() method. This method is called before invoking any of component/presenter signal handlers, and before presenter startup, action<> and render<> methods., _(*4)

With this package you can specify the access rules via attributes on any of the mentioned methods, or on presenter class. To enable this feature simple use SecurityAnnotations trait in any presenter or component and make sure RequirementsChecker service gets injected via injectRequirementsChecker() - with default Nette configuration this should work on presenters out of the box, but you need to take care of components, e.g. by enabling inject calls., _(*5)

Example:, _(*6)

use Nepada\SecurityAnnotations\Annotations\Allowed;
use Nepada\SecurityAnnotations\Annotations\LoggedIn;
use Nepada\SecurityAnnotations\Annotations\Role;

/**
 * To access this presenter the user must be logged in.
 */
 #[LoggedIn]
class SecuredPresenter extends Nette\Application\UI\Presenter
{

    use Nepada\SecurityAnnotations\SecurityAnnotations;

    #[Role("admin", "superadmin")]
    public function actionForAdmins(): void
    {
        // Only users with role admin or superadmin are allowed here.
    }

     #[Allowed(resource: "world", privilege: "destroy")]
    public function handleDestroyWorld(): void
    {
        // Only users with specific permission are allowed to call this signal.
    }

}

The attributes and rules they enforce are completely customizable (see below), however the default setup comes with three predefined rules:, _(*7)

• LoggedIn - checks whether the user is logged in.
• Role("admin", "superadmin") - checks whether the user has at least one of the specified roles. If you use Nette\Security\Permission as your authorizator, then role inheritance is taken into account, i.e. users that have at least one role that inherits from at least one of the specified roles are allowed as well.
• Allowed(resource: "world", privilege: "destroy") - checks whether the user has at least one role that is granted the specified privilege on the specified resource.

Securing components

Properly securing components is a tricky business, take a look at the following example:, _(*8)

use Nepada\SecurityAnnotations\Annotations\LoggedIn;

class SecuredPresenter extends Nette\Application\UI\Presenter
{

    use Nepada\SecurityAnnotations\SecurityAnnotations;

    #[LoggedIn]
    public function actionDefault(): void
    {
        // ...
    }

    protected function createComponentForm(): Nette\Application\UI\Form
    {
        $form = new Nette\Application\UI\Form();
        $form->addSubmit('Do something dangerous');
        $form->onSuccess[] = function (Nette\Application\UI\Form $form): void {
            // ...
        };
        return $form;
    }

}

Securing presenter action<> (or render<>) methods is not sufficient! All it takes is a one general route in your router, e.g. a very common Route('<presenter>/<action>'), and anyone may successfully submit the form by sending POST request to /secured/foo URL., _(*9)

You should always check user's permissions when creating the component. To make your life easier there is SecuredComponents trait that calls the standard Nette\Application\UI\Component::checkRequirements() method before calling the component factory (nette/application 3.2.2 and later performs this check natively, making the trait obsolete). Combining it with SecurityAnnotations it allows you to control access to components via attributes on createComponent<> methods., _(*10)

Customizing access validators

• You can disable the default set of validators by enableDefaultValidators: false.
• You can also define your own validators, i.e. services implementing Nepada\SecurityAnnotations\AccessValidators\AccessValidator interface in validators configuration section.

securityAnnotations:
    enableDefaultValidators: false # disable default set of validators
    validators:
        - MyRoleAccessValidator # define validator by class name
        - @fooAccessValidator # define validator by service reference

services:
    fooAccessValidator: FooAccessValidator(%fooParameter%)

How do access validators work?

Every access validator implements Nepada\SecurityAnnotations\AccessValidators\AccessValidator interface. The access validator specifies which attribute type it supports via its public API., _(*11)

When checking the requirements PHP attributes are passed one by one to associated access validator for inspection. Based on the attribute value the validator decides either to deny access (throws Nette\Application\BadRequestException), or grant access (no exception is thrown)., _(*12)