Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:extensions:cloudfile:permission [2014/08/06 22:24]
swarnat
en:extensions:cloudfile:permission [2014/08/06 22:29] (current)
swarnat
Line 9: Line 9:
 **Example** **Example**
 The path The path
-/​main/​sub/​directory/​+**/​main/​sub/​directory/​**
 will checked like this: will checked like this:
   - Did I have access to **/**, if not prevent complete access   - Did I have access to **/**, if not prevent complete access
Line 50: Line 50:
  ba  ba
 </​code>​ </​code>​
-And you prohibit the access of /a , allow the access to /a/ac/ace and allow /b for the user .+And you **prohibit the access of /a , allow the access to /a/ac/acd and allow /b** for the user .
 Then the user will see the following filesystem: Then the user will see the following filesystem:
 <​code>​ <​code>​
Line 60: Line 60:
  ba  ba
 </​code>​ </​code>​
-And no **/a/ab** or **/a/ac/ace**.  +And no **/a/ab** or **/a/ac/acd**.  
-Also the user won't see any content of the directories below **/a/ac/ace**. +Also the user won't see any other content of the directories below **/a/ac/acd**. 
-The system will manage the directories to makes it possible to navigate from the root to the directory the user could access.+ 
 +The system will manage the directories to makes it possible to navigate from the root to the directory the user could access. But nothing else is visible.
 </​WRAP>​ </​WRAP>​
 +
 +You could try this best if you setup the "​filesystem"​ provider and try it in local filesystem.
 +
 +I decide to implement the permission system in this way, because this system makes it easier to allow only single directories and prohibit access to all other directories.
 +Also it isn't more work if you want to allow almost all directories and only prevent access to single directories.