Access Control"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
Access control is a way you to give your users different permissions while working on folders and files. The default setting in the config.php files gives permission to every user and permits all the options. In order to change this configuration you must firstly know the basic of the '''AccessControl''' function placed in the ckfinder.config file. 
+
__TOC__
  
−
The syntax of the function:
+
Access Control Lists (ACL) are ways you to give your users different permissions while working on folders and files. The default settings in the config.ascx file give full permissions to all users. In order to change this configuration you must firstly know the basics of the '''AccessControl''' settings, which can be found in the config.ascx file. 
−
<pre>&lt;AccessControl
+
 
−
role = "*"
+
This is the syntax for these settings:
−
resourceType = "*"
+
<pre>AccessControl acl = AccessControl.Add();
−
folder = "/"  
+
acl.Role = "*";
−
folderView = "true"
+
acl.ResourceType = "*";
−
folderCreate = "true"
+
acl.Folder = "/";
−
folderRename = "true"
+
 
−
folderDelete = "true"
+
acl.FolderView = true;
−
fileView = "true"
+
acl.FolderCreate = true;
−
fileUpload = "true"
+
acl.FolderRename = true;
−
fileRename = "true"
+
acl.FolderDelete = true;
−
fileDelete = "true"
+
 
−
/&gt;
+
acl.FileView = true;
 +
acl.FileUpload = true;
 +
acl.FileRename = true;
 +
acl.FileDelete = true;
 
</pre>  
 
</pre>  
−
The three most important parameters of the "'''Access Control'''" function are:
+
Basically, a single Access Control setting is defined in an instance of the AccessControl class, created with '''AccessControl.Add()'''.<br>
 +
 
 +
The most important (and required) properties of the "'''AccessControl'''" objects are: '''Role''', '''ResourceType''' and '''Folder.'''<br>
 +
 
 +
== Role<br> ==
 +
 
 +
The '''Role''' property sets the type of user defined by the ACL. If set to asterisk (*) it is treated as "all users". You may set this parameter to other names like "Admin" or "Redator". The name of the user type will be directly connected to the function the user are allowed to use. See [[#RoleSessionVar|RoleSessionVar]] for more information.<br>
 +
 
 +
== ResourceType ==
 +
 
 +
The '''ResourceType''' property defines the resource type related to a specific ACL setting. See Resource Types for more information.<br>
 +
 
 +
If this property is set to asterisk (*) the defined ACL is valid for all resource settings definined in the configuration file.<br>
  
−
=== role ===
+
== Folder ==
  
−
The '''role''' is an attribute which sets the type of the user. It is set to "*" as default and you may treat as "every user". You may set this parameter to other name like: "user or "limited_functions". The name of the user type will be directly connected to the function the user may use.
+
You can apply ACL settings to specific folders by using the'''Folder''' property. Just set it to the folder path. The settings will be recursivelly applied to all folders inside that path.
  
−
=== resourceType ===
+
== Folder and File Options ==
  
−
The '''resourceType''' defines the resources handled in CKFinder. A resource type is nothing more than a way to group files under different paths, each one having different configuration settings. E.g. Images, Flash, Files.It is set to "*" as default and means that all of the resources are available.
+
All other properties are related to the specific features to enabled/disable by the ACL setting. Just set them to '''true''' or '''false''' according to your needs. True of course enables an option, false disables it.
  
−
=== folder ===
+
For example, just add the following if you want to restrict the user to upload, rename or delete files in the "/Company/Logos" folder of the resource type "Images":
 +
<pre>acl = AccessControl.Add();
 +
acl.Role = "*";
 +
acl.ResourceType = "Images";
 +
acl.Folder = "/Company/Logos/";
  
−
'''Folder''' determines where your limitations will be used. By placing the folders name you specify the place you want to put your restrictions in. It is set to '/' as default so no folder is set.
+
acl.FileUpload = false;
 +
acl.FileRename = false;
 +
acl.FileDelete = false;
 +
</pre>
 +
Note that we are reusing the "acl" variable defined previously. You may have as many AccessControl.Add() calls as you want.
  
−
=== folder and file options <br> ===
+
The above example only refers to file operations in the "/Company/Logos" folder itself and all its child folders. It doesn't restrict operations on the folder so the user can delete or rename the folder.
  
−
The rest of the variables are bool type and can be set as '''true''' or '''false'''. True of course enables an option, false disables it.<br>Example:<br>If you want to restrict the upload, rename or delete of files in the "Logos" folder of the resource type "Images":
+
In order to limit users from modifying the folder (not its contents) you should change the permissions in its parent folder. For example:
−
<pre>&lt;AccessControl
+
<pre>acl = AccessControl.Add();
−
role = "*"
+
acl.Role = "*";
−
resourceType = "Images"
+
acl.ResourceType = "Images";
−
folder = "/Logos"  
+
acl.Folder = "/Company/"  
  
−
fileUpload = "false"
+
folderCreate = true;
−
fileRename = "false"
+
folderRename = false;
−
fileDelete = "false"
+
folderDelete = false;
−
/&gt;
 
 
</pre>  
 
</pre>  
−
The above example only refers to file operations in the folder '/Logos' itself. It doesn't restrict operations on the folder so the user can delete or rename the folder. In order to limit users ability to modify the folder (not its context) you should change permissions in the parent folder.<br>Example:
+
Now a user can view and create a folder, but s/he will not be unable to rename or delete it. This is the best way to secure your folders from unauthorized access.
−
<pre>&lt;AccessControl
 
−
role = "*"
 
−
resourceType = "Images"
 
−
folder = "/"
 
  
−
folderView = "true"
+
== RoleSessionVar<br> ==
−
folderCreate = "true"
 
−
folderRename = "false"
 
−
folderDelete = "false"
 
−
/&gt;</pre>
 
−
Now a user can view and create a folder, but he will be unable to rename or delete it. This is the best way to secure your folders from unauthorized access.
 
  
−
=== sessions ===
+
CKFinder uses the server side session to identify the current user role. In order to enable the Access Control settings for different users, you should initialize a session variable when the user logs on your system.
  
−
In order to enable the access control options for different users you should initialize a session.
+
To indicate CKFinder the name of the session variable to use to identify the user role, just use the RoleSessionVar setting. For example:
−
<pre>roleSessionVar = "CKFinder_UserRole"
+
<pre>RoleSessionVar = "CKFinder_UserRole";
 
</pre>  
 
</pre>  
−
The session is a mechanism which will allow you to give different permissions to different users. <br>Example:<br>In your config.php file you create three different roles:
+
In the above example, the "CKFinder_UserRole" session variable value will be used to match the ACL entries defined previously. See [[#Role|Role]], above in this page.
 +
 
 +
For example, in the config.ascx file you may the following three different roles:
 +
 
 +
The '''Admin''' role, which has full permissions:
 +
<pre>AccessControl acl = AccessControl.Add();
 +
acl.Role = "Admin";
 +
acl.ResourceType = "*";
 +
acl.Folder = "/";
 +
 
 +
acl.FolderView = true;
 +
acl.FolderCreate = true;
 +
acl.FolderRename = true;
 +
acl.FolderDelete = true;
  
−
First role '''admin''' '''(*)''':
+
acl.FileView = true;
−
<pre>$config['AccessControl'][] = Array(
+
acl.FileUpload = true;
−
'role' =&gt; '*',
+
acl.FileRename = true;
−
'resourceType' =&gt; '*',
+
acl.FileDelete = true;
−
'folder' =&gt; '/',
+
</pre>
−
'folderView' =&gt; false,
+
The '''User''' role, which cannot rename or delete files or folders:
−
'folderCreate' =&gt; false,
+
<pre>AccessControl acl = AccessControl.Add();
−
'folderRename' =&gt; false,
+
acl.Role = "User";
−
'folderDelete' =&gt; false,
+
acl.ResourceType = "*";
 +
acl.Folder = "/";
  
−
'fileView' =&gt; false,
+
acl.FolderView = true;
−
'fileUpload' =&gt; false,
+
acl.FolderCreate = true;
−
'fileRename' =&gt; false,
+
acl.FolderRename = false;
−
'fileDelete' =&gt; false);</pre>
+
acl.FolderDelete = false;
−
Second role '''user''':
 
−
<pre>$config['AccessControl'][] = Array(
 
−
'role' =&gt; 'user',
 
−
'resourceType' =&gt; '*',
 
−
'folder' =&gt; '/',
 
−
'folderView' =&gt; true,
 
−
'folderCreate' =&gt; true,
 
−
'folderRename' =&gt; false,
 
−
'folderDelete' =&gt; false,
 
  
−
'fileView' =&gt; true,
+
acl.FileView = true;
−
'fileUpload' =&gt; true,
+
acl.FileUpload = true;
−
'fileRename' =&gt; false,
+
acl.FileRename = false;
−
'fileDelete' =&gt; false);&nbsp;</pre>  
+
acl.FileDelete = false;
−
Third role '''guest''':
+
</pre>  
−
<pre>$config['AccessControl'][] = Array(
+
The '''Guest''' role, which can only view the folders contents:
−
'role' =&gt; 'guest',
+
<pre>AccessControl acl = AccessControl.Add();
−
'resourceType' =&gt; '*',
+
acl.Role = "Guest";
−
'folder' =&gt; '/',
+
acl.ResourceType = "*";
−
'folderView' =&gt; true,
+
acl.Folder = "/";
−
'folderCreate' =&gt; false,
 
−
'folderRename' =&gt; false,
 
−
'folderDelete' =&gt; false,
 
  
−
'fileView' =&gt; true,
+
acl.FolderView = true;
−
'fileUpload' =&gt; false,
+
acl.FolderCreate = false;
−
'fileRename' =&gt; false,
+
acl.FolderRename = false;
−
'fileDelete' =&gt; false); &nbsp;</pre>
+
acl.FolderDelete = false;
−
You've created three different users permissions.
 
  
−
'''Important:''' Note that when the role is set to '''*''' the user always has administrative privileges even though all the options are set to '''false'''.
+
acl.FileView = true;
 +
acl.FileUpload = false;
 +
acl.FileRename = false;
 +
acl.FileDelete = false;
 +
</pre>
 +
'''<br>'''

Latest revision as of 07:46, 28 May 2010

Access Control Lists (ACL) are ways you to give your users different permissions while working on folders and files. The default settings in the config.ascx file give full permissions to all users. In order to change this configuration you must firstly know the basics of the AccessControl settings, which can be found in the config.ascx file. 

This is the syntax for these settings: 

AccessControl acl = AccessControl.Add();
acl.Role = "*";
acl.ResourceType = "*";
acl.Folder = "/";

acl.FolderView = true;
acl.FolderCreate = true;
acl.FolderRename = true;
acl.FolderDelete = true;

acl.FileView = true;
acl.FileUpload = true;
acl.FileRename = true;
acl.FileDelete = true;

Basically, a single Access Control setting is defined in an instance of the AccessControl class, created with AccessControl.Add().

The most important (and required) properties of the "AccessControl" objects are: Role, ResourceType and Folder.

Role

The Role property sets the type of user defined by the ACL. If set to asterisk (*) it is treated as "all users". You may set this parameter to other names like "Admin" or "Redator". The name of the user type will be directly connected to the function the user are allowed to use. See RoleSessionVar for more information.

ResourceType

The ResourceType property defines the resource type related to a specific ACL setting. See Resource Types for more information.

If this property is set to asterisk (*) the defined ACL is valid for all resource settings definined in the configuration file.

Folder

You can apply ACL settings to specific folders by using theFolder property. Just set it to the folder path. The settings will be recursivelly applied to all folders inside that path.

Folder and File Options

All other properties are related to the specific features to enabled/disable by the ACL setting. Just set them to true or false according to your needs. True of course enables an option, false disables it.

For example, just add the following if you want to restrict the user to upload, rename or delete files in the "/Company/Logos" folder of the resource type "Images": 

acl = AccessControl.Add();
acl.Role = "*";
acl.ResourceType = "Images";
acl.Folder = "/Company/Logos/";

acl.FileUpload = false;
acl.FileRename = false;
acl.FileDelete = false;

Note that we are reusing the "acl" variable defined previously. You may have as many AccessControl.Add() calls as you want.

The above example only refers to file operations in the "/Company/Logos" folder itself and all its child folders. It doesn't restrict operations on the folder so the user can delete or rename the folder.

In order to limit users from modifying the folder (not its contents) you should change the permissions in its parent folder. For example: 

acl = AccessControl.Add();
acl.Role = "*";
acl.ResourceType = "Images";
acl.Folder = "/Company/" 

folderCreate = true;
folderRename = false;
folderDelete = false;

Now a user can view and create a folder, but s/he will not be unable to rename or delete it. This is the best way to secure your folders from unauthorized access.

RoleSessionVar

CKFinder uses the server side session to identify the current user role. In order to enable the Access Control settings for different users, you should initialize a session variable when the user logs on your system.

To indicate CKFinder the name of the session variable to use to identify the user role, just use the RoleSessionVar setting. For example: 

RoleSessionVar = "CKFinder_UserRole";

In the above example, the "CKFinder_UserRole" session variable value will be used to match the ACL entries defined previously. See Role, above in this page.

For example, in the config.ascx file you may the following three different roles:

The Admin role, which has full permissions: 

AccessControl acl = AccessControl.Add();
acl.Role = "Admin";
acl.ResourceType = "*";
acl.Folder = "/";

acl.FolderView = true;
acl.FolderCreate = true;
acl.FolderRename = true;
acl.FolderDelete = true;

acl.FileView = true;
acl.FileUpload = true;
acl.FileRename = true;
acl.FileDelete = true;

The User role, which cannot rename or delete files or folders: 

AccessControl acl = AccessControl.Add();
acl.Role = "User";
acl.ResourceType = "*";
acl.Folder = "/";

acl.FolderView = true;
acl.FolderCreate = true;
acl.FolderRename = false;
acl.FolderDelete = false;

acl.FileView = true;
acl.FileUpload = true;
acl.FileRename = false;
acl.FileDelete = false;

The Guest role, which can only view the folders contents: 

AccessControl acl = AccessControl.Add();
acl.Role = "Guest";
acl.ResourceType = "*";
acl.Folder = "/";

acl.FolderView = true;
acl.FolderCreate = false;
acl.FolderRename = false;
acl.FolderDelete = false;

acl.FileView = true;
acl.FileUpload = false;
acl.FileRename = false;
acl.FileDelete = false;


Retrieved from "https://docs-old.ckeditor.com/index.php?title=CKFinder_1.x/Developers_Guide/ASP.NET/Configuration/Access_Control&oldid=3409"
This page was last edited on 28 May 2010, at 07:46.