Is it possible to create general policy for ORM resolver? about authorization

[markstory]

The ORM resolver doesn't currently support a fallback/default policy. Would you be using a fallback to define default permissions or just trying to avoid having to define policy methods?

[ulziibadrakh-p]

I am trying to make authorization that logged in user can access Index, View, Add actions and check owner on Edit, Delete actions for all controller.

class GeneralPolicy
{

    public function canView()
    {
        return true;
    }

    public function canCreate()
    {
        return true;
    }

    public function canEdit(IdentityInterface $user,  $model)
    {
        // logged in users can edit their own models.
        return $this->isAuthor($user, $model);
    }

    public function canDelete(IdentityInterface $user,  $model)
    {
        // logged in users can delete their own models.
        return $this->isAuthor($user, $model);
    }

    protected function isAuthor(IdentityInterface $user,  $model)
    {
        return $model->user_id === $user->id;
    }
}

May be (User class as identity) is solution but I don't understand clearly.

[markstory]

The user class as identity would be helpful, but more is needed. Right now you would need to use the chain resolver and build a resolver class that always returns your GeneralPolicy class. Then you could put the OrmResolver first in the chain, and your generic resolver second. Doing this would let you to add specific policies for models as you need them.

[othercorey]

Closing this as the solution is a custom resolver.