1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
<?xml version="1.0" encoding="UTF-8"?>
<!-- Reviewed: no -->
<sect1 id="zend.acl.advanced">
<title>Advanced Usage</title>
<sect2 id="zend.acl.advanced.storing">
<title>Storing ACL Data for Persistence</title>
<para>
<classname>Zend_Acl</classname> 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
<acronym>ACL</acronym> data. Its complete <acronym>PHP</acronym> implementation enables
customized administration tools to be built upon <classname>Zend_Acl</classname> with
relative ease and flexibility. Many situations require some form of interactive
maintenance of the <acronym>ACL</acronym>, and <classname>Zend_Acl</classname> provides
methods for setting up, and querying against, the access controls of an application.
</para>
<para>
Storage of <acronym>ACL</acronym> data is therefore left as a task for the developer,
since use cases are expected to vary widely for various situations. Because
<classname>Zend_Acl</classname> is serializable, <acronym>ACL</acronym> objects may be
serialized with <acronym>PHP</acronym>'s <ulink url="http://php.net/serialize">
<methodname>serialize()</methodname></ulink> function, and the results may be
stored anywhere the developer should desire, such as a file, database, or caching
mechanism.
</para>
</sect2>
<sect2 id="zend.acl.advanced.assertions">
<title>Writing Conditional ACL Rules with Assertions</title>
<para>
Sometimes a rule for allowing or denying a 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. <classname>Zend_Acl</classname> has built-in support for
implementing rules based on whatever conditions the developer needs.
</para>
<para>
<classname>Zend_Acl</classname> provides support for conditional rules with
<classname>Zend_Acl_Assert_Interface</classname>. In order to use the rule assertion
interface, a developer writes a class that implements the
<methodname>assert()</methodname> method of the interface:
</para>
<programlisting language="php"><![CDATA[
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)
{
// ...
}
}
]]></programlisting>
<para>
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 <constant>TRUE</constant>.
</para>
<programlisting language="php"><![CDATA[
$acl = new Zend_Acl();
$acl->allow(null, null, null, new CleanIPAssertion());
]]></programlisting>
<para>
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.
</para>
<para>
The <methodname>assert()</methodname> method of an assertion object is passed the
<acronym>ACL</acronym>, role, resource, and privilege to which the authorization query
(i.e., <methodname>isAllowed()</methodname>) applies, in order to provide a context for
the assertion class to determine its conditions where needed.
</para>
</sect2>
</sect1>
<!--
vim:se ts=4 sw=4 et:
-->
|
