This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
rootdir [2022/02/07 16:32] yves [Security] |
rootdir [2022/03/25 11:59] yves [Configuration] |
||
---|---|---|---|
Line 35: | Line 35: | ||
==== Configuration ==== | ==== Configuration ==== | ||
- | We have a [[rootdir_config|separate section]] in this wiki that takes you through the different steps that you can take to [[rootdir_config|configure root directories and mounting points]]. | + | **Root directories management** |
- | We also talk about the security precautions that you can take when configuring these. | + | Root directories can be managed by selecting the "Root directories" option under the "Settings" section in the left menu. |
- | ==== Security ==== | + | {{ :roots.png?nolink&400 |}} |
- | Root directories can be either public or private. | + | The list displays all the configured root directories and provides options to add new, edit and delete entries. |
- | Public root directories can be accesses by anybody who is a registered user in the PMA.core user repository. | + | * The "Offline" column indicates whether or not a root directory is enabled. An offline root directory is not advertised by the system and its contents are not available to the end-users. |
+ | * The "Path exists" column indicates whether or not the system is able to mount a root directory's path and access it's contents. For example a root directory that points to a local file system folder, that has been deleted, will not have the "Path exists" column checked. | ||
- | 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]]. | + | We have a [[rootdir_config|separate section]] in this wiki that takes you through the different steps that you can take to [[rootdir_config|configure root directories and mounting points]]. |
+ | |||
+ | Root-directories can be labeled public or private, which allow you to [[rootdir_security#public_vs_private|take security precautions when configuring these]]. | ||
+ | |||
+ | ==== Security ==== | ||
+ | |||
+ | Root directories can be either [[rootdir_security#public_vs_private|public or private]]. | ||
Who's accessed what (either public or private) folder can be monitored via the Access log tab. | Who's accessed what (either public or private) folder can be monitored via the Access log tab. | ||
{{ ::access_log.png?nolink&400 |}} | {{ ::access_log.png?nolink&400 |}} | ||
- | |||
==== Logging ==== | ==== Logging ==== | ||
Line 58: | Line 64: | ||
You can monitor logs for several kinds of acivity: | You can monitor logs for several kinds of acivity: | ||
+ | {{ :rootdir_logs.png?direct&400 |}} | ||
+ | === Audit trail === | ||
+ | |||
+ | The audit trail tab conbines any operations that were performed on both root directory entries and underlaying mounting point entries. | ||
+ | |||
+ | {{ :rootdir_audit.png?direct&400 |}} | ||
+ | |||
+ | The presented information [[21_cfr_part_11|21 CFR pârt 11 compliant]]. | ||
+ | |||
+ | === Activity log === | ||
+ | |||
+ | In addition to an audit trail, an activity log is available that chronologically tell you which user has been accessing what slides in the root directory: | ||
+ | |||
+ | {{ :rootdir_activity.png?direct&400 |}} | ||
==== Integrity check ==== | ==== Integrity check ==== | ||
- | If you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder by going to | + | When problems persist over time, a structured and proactive approach is warranted. |
+ | |||
+ | When you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder: | ||
+ | |||
+ | {{ :rootdir_integrity.png?direct&400 |}} | ||
+ | |||
+ | This attempts to read all slides in a folder and reports on the ones that fail. You should then [[format_troubleshoot|try to find out why such slides cannot be read]]. | ||
+ | For problems that only occur occasionally and don't appear to be persistent, [[elmah|Elmah logs]] are available to assist in for ad-hoc troubleshooting. |