2.3. Advanced Use
Prev | Chapter 2. Zend_Acl | Next

## 2.3. Advanced Use

### 2.3.1. Storing ACL Data for Persistence

Zend_Acl was designed in such a way that it does not require any particular backend technology such as a database or cache server for storage of the ACL data. Its complete PHP implementation enables customized administration tools to be built upon Zend_Acl with relative ease and flexibility. Many situations require some form of interactive maintenance of the ACL, and Zend_Acl provides methods setting up, and querying against, the access controls of an application.

Storage of ACL data is therefore left as a task for the developer, since use cases are expected to vary widely for various situations. Because Zend_Acl is serializable, ACL objects may be serialized with PHP's `serialize()` function, and the results may be stored anywhere the developer should desire, such as a file, database, or caching mechanism.

### 2.3.2. Writing Conditional ACL Rules with Assertions

Sometimes a rule for allowing or denying an Role access to a Resource should not be absolute but dependent upon various criteria. For example, suppose that certain access should be allowed, but only between the hours of 8:00am and 5:00pm. Another example would be denying access because a request comes from an IP address that has been flagged as a source of abuse. Zend_Acl has built-in support for implementing rules based on whatever conditions the developer needs.

Zend_Acl provides support for conditional rules with `Zend_Acl_Assert_Interface`. In order to use the rule assertion interface, a developer writes a class that implements the `assert()` method of the interface:

    <?php
    require_once 'Zend/Acl/Assert/Interface.php';

    class CleanIPAssertion implements Zend_Acl_Assert_Interface
    {
        public function assert(Zend_Acl $acl, Zend_Acl_Role_Interface $role = null,
                               Zend_Acl_Resource_Interface $resource = null, $privilege = null)
        {
            return $this->_isCleanIP($_SERVER['REMOTE_ADDR']);
        }

        protected function _isCleanIP($ip)
        {
            // ...
        }
    }

Once an assertion class is available, the developer must supply an instance of the assertion class when assigning conditional rules. A rule that is created with an assertion only applies when the assertion method returns true.

    <?php
    require_once 'Zend/Acl.php';

    $acl = new Zend_Acl();
    $acl->allow(null, null, null, new CleanIPAssertion());

The above code creates a conditional allow rule that allows access to all privileges on everything by everyone, except when the requesting IP is "blacklisted." If a request comes in from an IP that is not considered "clean," then the allow rule does not apply. Since the rule applies to all Roles, all Resources, and all privileges, an "unclean" IP would result in a denial of access. This is a special case, however, and it should be understood that in all other cases (i.e., where a specific Role, Resource, or privilege is specified for the rule), a failed assertion results in the rule not applying, and other rules would be used to determine whether access is allowed or denied.

The `assert()` method of an assertion object is passed the ACL, Role, Resource, and privilege to which the authorization query (i.e., `isAllowed()`) applies, in order to provide a context for the assertion class to determine its conditions where needed.

Prev | Up | Next
2.2. Refining Access Controls | Home | Chapter 3. Zend_Auth