Differences

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

--- rootdir_security [2022/02/11 12:39]
yves [Access control lists]
+++ rootdir_security [2022/08/06 19:34]
yves [Accessing secured content]
@@ Line 7: / Line 7: @@
       * Configure public/secret key combinations for S3 resources
       * 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
@@ Line 16: / Line 16: @@
 Based on the type of data storage that a root directory's mounting point refers to, the configuration offers different options:
-=== Local hard disk entry points ===
+  * [[rootdir_local|Local hard disk entry points]]
+  * [[rootdir_network|Network storage and UNC paths]]
+  * [[rootdir_s3|S3 storage]]
+  * [[rootdir_azure|Azure storage]]
-If you want to expose a local folder on the server's hard disk as a root directory in PMA.core, the simplest way to do this is by giving the IIS user account access rights to the folder using the Windows Explorer:
+=== Azure storage ===
-{{ :rootdir_local10.png?direct&400 |}}
+Microsoft Azure has its own protocol, and so we provide a separate mounting point type of it.
+Let's say that you have an Azure container defined and put some slides in it already:
-=== Network storage (UNC paths) ===
+{{ :rootdir_azure_10.png?direct&400 |}}
-Pathomation runs under a certain application pool. This application pool is associated with a user identify, which may not have access to the network path that you try to access. Giving access for the application pool to access the network resource may be difficult for a variety of reasons.
+You can convert these credentials in a connectionstring:
-If you can't immediately access the network path with default (i.e. application pool) credentials, you can provide additional information.
+''%%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/;%%''
-In the case below we've created a dedicated pma_read user that is permitted to acces the shared \\MALTA1767\reference path:
+This text snippet is then pasted in the connection string field of the mounting point properties:
-{{ :rootdir_network10.png?direct&400 |}}
+{{ :rootdir_azure_20.png?direct&400 |}}
+If all goes well, you can now serve your slides from your Azure storage repositories.
-=== S3 storage ===
+==== Public vs private ====
-=== Azure storage ===
+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":
-==== Public vs private ====
+{{ :rootdir_public_private_switch.png?direct&200 |}}
-Public root directories can be accesses by anybody who is a registered user in the PMA.core user repository.
+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 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]].
+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 ====
@@ Line 51: / Line 56: @@
 {{ :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 |}}

PMA.core 3.0.1

User Tools

Site Tools

Differences

Page Tools