CKFinder 1.x/Server Side Integration/Access Control List - Revision history

Admin: moved CKFinder/Server Side Integration/Access Control List to CKFinder 1.x/Server Side Integration/Access Control List

2010-05-28T06:46:33Z

moved CKFinder/Server Side Integration/Access Control List to CKFinder 1.x/Server Side Integration/Access Control List

Wiktor at 14:37, 16 January 2008

2008-01-16T14:37:05Z

Wiktor at 14:18, 16 January 2008

2008-01-16T14:18:53Z

Wiktor at 14:18, 16 January 2008

2008-01-16T14:18:33Z

Wiktor at 14:18, 16 January 2008

2008-01-16T14:18:15Z

Wiktor at 14:18, 16 January 2008

2008-01-16T14:18:03Z

Wiktor: New page: == ACL – Access Control List == CKFinder comes with a powerful ACL feature, which makes it possible to define ACL settings at any level in the repository directories and subfolders. It ...

2008-01-16T14:17:44Z

New page: == ACL – Access Control List == CKFinder comes with a powerful ACL feature, which makes it possible to define ACL settings at any level in the repository directories and subfolders. It ...

New page

== ACL – Access Control List ==

CKFinder comes with a powerful ACL feature, which makes it possible to define ACL settings at any level in the repository directories and subfolders. It implements also a simple role system for ACLs. In the configuration file, many <AccessControl /> nodes can be created to define ACLs. All attributes defined in AccessControl nodes are optional, and each one overrides ACLs defined for parent folders. For example, suppose the following ACLs are defined:
<pre><AccessControl
role = "*"
resourceType = "*"
folder = "/"
folderView = "true"
folderCreate = "true"
fileUpload = "true"
/>
<AccessControl
role = "*"
resourceType = "Images"
folder = "/My Test/Other Folder/"
fileUpload = "false"
/></pre>
The above should then reflect in the connector execution by returning the following values for FileUpload:

* Type = Files - / : true
* Type = Files - /My Test/ : true
* Type = Files - /My Test/Other Folder/ : true
* Type = Images - /My Test/ : true
* Type = Images - /My Test/Other Folder/ : false
* Type = Images - /My Test/Other Folder/Folder 3/ : false

<br>The “*” wildcard may be used for “role” and “resurceType” to include all.

=== Roles ===

By setting the '''roleSessionVar''' attribute, the end developer can point the connector to a session variable which contains the name of the role of the session user. This name would then be used to calculate the ACL.''''

=== ACL Representation ===

When sending ACL information to CKFinder, the connector sends a “bit mask” represented by an integer value. Each folder contains a computed aggregated ACL bit mask.

The following is the representation of all used bits in the mask:
<pre>enum AccessControlRules
{
FolderView = 1,
FolderCreate = 2,
FolderRename = 4,
FolderDelete = 8,
FileView = 16,
FileUpload = 32,
FileRename = 64,
FileDelete = 128
}</pre>

← Older revision		Revision as of 14:37, 16 January 2008
Line 1:		Line 1:
		+	{{CKFinder_SSI_Warning}}
	== ACL – Access Control List ==		== ACL – Access Control List ==

← Older revision		Revision as of 14:18, 16 January 2008
Line 28:		Line 28:

	<br>The “*” wildcard may be used for “role” and “resurceType” to include all.		<br>The “*” wildcard may be used for “role” and “resurceType” to include all.
−

	=== Roles ===		=== Roles ===

@@ Line 2: / Line 2: @@
 CKFinder comes with a powerful ACL feature, which makes it possible to define ACL settings at any level in the repository directories and subfolders. It implements also a simple role system for ACLs. <br>
 In the configuration file, many &lt;AccessControl /&gt; nodes can be created to define ACLs. All attributes defined in AccessControl nodes are optional, and each one overrides ACLs defined for parent folders. For example, suppose the following ACLs are defined:
 <pre>&lt;AccessControl

← Older revision	Revision as of 06:46, 28 May 2010
(No difference)

@@ Line 1: / Line 1: @@
 == ACL – Access Control List ==
-CKFinder comes with a powerful ACL feature, which makes it possible to define ACL settings at any level in the repository directories and subfolders. It implements also a simple role system for ACLs. In the configuration file, many &lt;AccessControl /&gt; nodes can be created to define ACLs. All attributes defined in AccessControl nodes are optional, and each one overrides ACLs defined for parent folders. For example, suppose the following ACLs are defined:
+CKFinder comes with a powerful ACL feature, which makes it possible to define ACL settings at any level in the repository directories and subfolders. It implements also a simple role system for ACLs. <br>
 <pre>&lt;AccessControl
   role = "*"