A client is requesting I provide a list of "people with access" to all folders an files within the company. This is a daunting task and I was wondering if there was a way to do this whether it be through Vault or by some other means.
Related
I'm in a very frustrating situation where we are trying to clean out a large amount of data in a TFVC repo on an Azure Devops Server installation. I am a domain admin, I am the SQL server admin, and an admin anywhere I can find throughout Devops.
Yet, I had multiple issues trying to delete the top level folders out of the repo due to needing Read or Commit permissions. So, I managed to navigate through all the different levels of folders and identify a few folders/files where inheritance was turned off and I didn't have permission, so I added myself, and voila was able to delete the folder/file.
However, I have one folder left that refuses to let me delete it. It tells me I need Commit permissions on the folder. There are no other folders/files under this folder that are visible.
I've searched high and low for anything that would let me "take ownership" or some how override these permissions that are possibly buried under this folder somewhere. I suspect maybe there is a deny or broken inheritance under this folder that prevents me from even seeing the data.
Is there anyway to gain access to this and delete this folder?
I want to add a group/user to an Azure DevOps project with just access to repositories and pipelines.
If I deny "View project-level information" they don't have access to the project at all.
If I allow the "View project-level information" it gives them a read-only access to the Project Settings including permissions to see users and members of other groups etc.
It seems unbelievable that such a basic security and privacy hole exists.
Am I missing something in the config because I have never seen this in any other application and I find it hard to believe that everyone else using Azure DevOps finds this acceptable.
The easiest equivalent is GitHub (that Microsoft now owns) and you can't see the project settings if you are just a contributor.
How do I give external contractors access to the project to work but prevent them from viewing the Project Settings?
There is no possibility to restrict access to the Team Project - Project Settings page. The only thing that comes close is the feature that is now in preview: Limit user visibility and collaboration to specific projects, which will enable you to restrict access to the Organization Settings. You could suggest this feature in the Microsoft Developer Community.
Every time I publish my project my folder permissons get removed. My project requires IIS APPPOOL\appPoolName and IUSR to have specific access right to specific folders.
Whats the best way to apply the folder permissons after the artifact has been published?
Not sure if totally get your point. You can use location elements in the web.config file, there is a lot of information on the web about that - this gives you a start: HOW TO: Control Authorization Permissions in an ASP.NET Application
Besides, for folder NTFS permissions here rather than web security permissions. You could also add a custom target to Visual Studio's web publishing pipeline. For detail ways please take a look at what Sayed Ibrahim Hashimi does here.
I am just trying to understand advantages of going to Team Drive for team repository on G suite vs using just shared folder on Google Drive. By searching different sources and doing testing I found the following results so far.
Frankly speaking this all makes me think whether Team Drive at the moment offers that much of advantage vs shared folder on Google Drive.
Questions:
1) did I miss anything in my analysis?
2) is there anything else Team Drive offers, which I did not mention?
3) Are there any other pitfalls (hidden problems) to use google Drive shared folders for team repository?
Advantages of Team Drive vs shared folder on Google Drive:
When contributors leaves the company, files they own will not disappear, if they were placed in Team Drive.
This however can he resolved, by simple automation, that manager becomes an owner of the files of people, reporting to him, who left the company
Edit access feature:
In a Team Drive you can have editors / contributors, who do not get permissions to delete or move files. Well, this is a good feature and clear advantage.
Limitations of Team Drive
One gets the same permissions for all files in one Team Drive.
Since most of the people contribute to some of the projects in one way or another, for us this means that everybody would get edit permissions for all project repositories in entire company, which is not what always desirable
Not possible to manage access permissions in hierarchical way
This is a consequence of the 1st one. In google drive say regional manager can have access permissions to entire region. He would then create subrigional folders and would assign them to sub-regional managers. Sub-regional managers would manager only their folders, but would not see other sub-regions folders. However permissions of regional manager would flow down and they will automatically see everything. Sub-regional managers would then create sub-folders for individual projects and give access permissions to individual Project Managers
In Team Drive such construction is not possible.
File and / or folders cannot be in multiple locations
This is really good feature of a Google Drive, which is missing in a Team Drive
Amount of subfolder levels limitation
It is 20 now, but still, this is a limitation
Amount of items (files/ folders) limitation
This is 400 k now, but still, this is a limitation
Limitations with migration of files from Google Drive to Team Drive
Links to folders will break.
Links to the folders do not get preserved, when they get migrated to Team Drive
Disappearing files / folders
If there was a file or folder, which was in multiple locations and one of these locations was in the folder, migrated to Team Drive, than this Drive folder/file would disappear from other locations as well, not only from the folder, which was explicitly migrated to Team Drive.
I can add something to your analysis:
Advantages of Team Drive
Drive File Stream: it's a Dropbox-like app, it will mount a virtual disk on your system. Files copied/moved there don't take up disk space.
Limitations of Team Drive
You can't share a folder, just singles files or the whole Team Drive. This is not something I would expect from an enterprise dedicated tool...
I have installed owncloud at a server.
https://cloudybox.tk
How can I restrict user to a specified folder.
Like, if a user signup, then he can access only to a folder named by his username.
So that i can start an online cloud storage website.
You should Nextcloud instead of Owncloud. It has more features, is more secure and fully open source. In Nextcloud you can put all users in one group and share a folder with this group. I think this is what you want.