Are Sharing Permissions on Project Repository Location necessary?
Question ID: 109984

Our ALM Production server has a D: drive partition which houses our Project Repository (folder is d:\alm\repository as directed for “repository” folder during install). It is currently configured as a Network Share, which is being flagged as a security vulnerability.

Is this necessary? If it is, what degree of permissions need to be set. We would rather have it locked down as much as possible. Interestingly, the D: drive partition on our Staging server is not configure as a Share.

Marked as spam
Posted by (Questions: 91, Answers: 5)
Asked on January 15, 2021 10:44 am
Answers (1)
Private answer

We sometimes SHARE the "log" folder or the "repository" folder so an admin can get to logs quickly or maintain project DBID.xml files to more easily re3store projects, but that need is rare -- especially if you can get to the ALM server's file system directly.

If you don't need to do that, then best NOT to share.

Either way ALM does not "know" about it being "shared".

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on January 15, 2021 10:49 am

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top