User Tools

Site Tools


rootdir_security

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
rootdir_security [2022/02/11 15:15]
yves [Accessing secured content]
rootdir_security [2022/03/14 13:48] (current)
yves [Public vs private]
Line 7: Line 7:
       * Configure public/​secret key combinations for S3 resources       * Configure public/​secret key combinations for S3 resources
       * Configure account credentials to be used when accessing a UNC network resource path       * Configure account credentials to be used when accessing a UNC network resource path
-  * Prevent users from access mounted content through root directories that they are or are not allowed to do+  * Prevent ​[[user_management|users]] from access mounted content through root directories that they are or are not allowed to do
       * Define Access control lists       * Define Access control lists
  
Line 86: Line 86:
 You can convert these credentials in a connectionstring:​ You can convert these credentials in a connectionstring:​
  
-''​DefaultEndpointsProtocol=https;​AccountName=pathomation;​AccountKey=SUPERSECRET;​BlobEndpoint=https://​pathomation.blob.core.windows.net/;​QueueEndpoint=https://​pathomation.queue.core.windows.net/;​TableEndpoint=https://​pathomation.table.core.windows.net/;​FileEndpoint=https://​pathomation.file.core.windows.net/;''​+''​%%DefaultEndpointsProtocol=https;​AccountName=pathomation;​AccountKey=SUPERSECRET;​BlobEndpoint=https://​pathomation.blob.core.windows.net/;​QueueEndpoint=https://​pathomation.queue.core.windows.net/;​TableEndpoint=https://​pathomation.table.core.windows.net/;​FileEndpoint=https://​pathomation.file.core.windows.net/;​%%''​
  
 This text snippet is then pasted in the connection string field of the mounting point properties: This text snippet is then pasted in the connection string field of the mounting point properties:
  
-{{ :rootdir_azure_10.png?​direct&​400 |}}+{{ :rootdir_azure_20.png?​direct&​400 |}}
  
 If all goes well, you can now serve your slides from your Azure storage repositories. If all goes well, you can now serve your slides from your Azure storage repositories.
Line 96: Line 96:
 ==== Public vs private ==== ==== Public vs private ====
  
-As you have more users and more root-directories,​ it becomes undesirable that everybody is allow to see everything.+As you have more [[user_management|users]] and more root-directories,​ it becomes undesirable that everybody is allowed ​to see everything.
  
 Therefore, root-directories can be marked "​public"​ or "​private":​ Therefore, root-directories can be marked "​public"​ or "​private":​
  
-Public root directories are marked "​public",​ it means every user has access to them. They can be accessed by anybody who is a registered user in the PMA.core user repository.+{{ :​rootdir_public_private_switch.png?​direct&​200 |}}
  
-Private root directories are marked "​private",​ it means only select users can see the content. They are only accessible by those who have been explicitly given access to be allowed to access the folder through the directory'​s [[acl|access control list]].+Public root directories are marked "​public",​ it means every user has access to them. They can be accessed by anybody who is a registered user in [[user_management|the PMA.core user repository]]. 
 + 
 +Private root directories are marked "​private",​ it means only select users can see the content. They are only accessible by those who have been explicitly given access to be allowed to access the folder through the directory'​s [[rootdir_security#​access_control_list|access control list]].
  
 ==== Access control lists ==== ==== Access control lists ====
Line 109: Line 111:
  
 {{ :​acl.png?​nolink&​400 |}} {{ :​acl.png?​nolink&​400 |}}
 +
 +An interactive overview grid is available via the Root directories management view:
 +
 +{{ :​rootdir_acl_20.png?​direct&​400 |}}
 +
 +As you get even more root-directories and more users, it is useful to get an overview of who has access to what. For that, you can request the ACL report from the root-directories view.
 +
 +{{ :​overview.png?​nolink&​400 |}}
 +
 +The resulting report looks like this:
 +
 +{{ :​overview2.png?​nolink&​400 |}}
 +
rootdir_security.1644581738.txt.gz · Last modified: 2022/02/11 15:15 by yves