Tuesday 25 May 2010 4:45:00 pm - 7 replies
This tutorial will show you how to deal with custom security policy limitations for your modules. Once read, you will be able to fully take advantage of the granularity in eZ Publish's security and access control system.
Tuesday 25 May 2010 10:34:35 pm
But I didn't get the eZJSCore example, the whole point of hasAccessToLimitation() is to not have to deal with limitations yourself. Without limitations you can just as well use "$user->hasAccessTo( $module, $function )" and "fetch( 'user', 'has_access_to', ... )".
phpdoc (1.1 and up):
/** * Check access to a specific module/function with limitation values. * See eZ Publish documentation on more info on module, function and * limitation values. Example: a user can have content/read permissions * but it can be limited to a specific limitation like a section, a node * or node tree. 1.x limitation: returns false if one of provided values * don't match but ignores limitations not specified in $limitations. * * @param string $module * @param string $function * @param array|null $limitations A hash of limitation keys and values * @param bool Lets you get some additional debug information if set to true, useful while developing. * @return bool */ public static function hasAccessToLimitation( $module, $function, $limitations = null, $debug = false )
Friday 28 May 2010 9:23:28 am
One thing that is not universally known: you can set up a set of policies of which at least one has to be matched to give access to a view, as well as defining a set of policies all of which have to be matched:
$ViewList = array( 'at_least_one' => array( 'functions' => array( 'func1 or func2' ) ), 'both' => array( 'functions' => array( 'func1', 'func2' ) ) ); $FunctionList = array( 'func1' => array(), 'func2' => array(), );
Modified on Friday 28 May 2010 9:24:19 am by Gaetano Giunta
You must be logged in to post messages in this topic!