<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 18 May 2013 03:42:43 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: Role Based Access Control in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/17668</guid>
      <link>http://www.phpdeveloper.org/news/17668</link>
      <description><![CDATA[<p>
On PHPMaster.com today there's a new tutorial posted (from <i>Martin Psinas</i>) about using <a href="http://phpmaster.com/role-based-access-control-in-php/">role-based access controls</a> in PHP-based applications. His method isn't based in any specific framework, so it's easily portable to just about any app out there.
</p>
<blockquote>
In this article I will discuss my personal favorite approach: role based access control (RBAC). RBAC is a model in which roles are created for various job functions, and permissions to perform certain operations are then tied to roles. A user can be assigned one or multiple roles which restricts their system access to the permissions for which they have been authorized.
</blockquote>
<p>
He starts with a warning that, if not properly maintained, a role-based system like this can get to be somewhat chaotic so a rules should be in place around the adding and removing of permissions at certain times. His functionality is based on a few database tables - roles, permissions and cross-reference tables between users/roles & permissions/roles. All of the code you'll need to implement the system is included in a Role class, the PrivilegedUser class and the methods you'll need to add/remove/check the logged in user's permissions.
</p>]]></description>
      <pubDate>Tue, 13 Mar 2012 13:10:05 -0500</pubDate>
    </item>
  </channel>
</rss>
