sh_<tenant>_adminsgroup members login to the Windows workstation and create folders for their separate projects to share data
[email protected]to request a shared drive. Once our technicians have enabled your shared drive, you will be notified and can continue to the next step
sh_<tenant>_adminswill have access to the shared drive by default. It is important for a member of
sh_<tenant>_adminsto create a folder structure inside the drive that can later be setup to allow access for users.
Data (H:), our top-level folder is
URSAWINLNX, and we have two project folders (
project2). We are using a top-level folder because the drive may have different names on the two different workstations.
sh_dev_test_adminsas our demonstration group that corresponds to
sh_<tenant>_adminsin a regular tenant, and thus has "Full control" of the folders
project2. We have given another group (
sh_dev_test_users) "Read, write & execute" access to the folder
project1but no access to
project2; you will see the repercussions of this in the next section.
sh_<tenant>_<groupname>become underlined. Click "OK" to return to the previous window
ls -lawould normally show the permissions on a folder or file, but in this case it returns the following
nfs4_getfaclto read the permissions of the folder to get the following response
nfs4_getfaclwe correctly see
sh_dev_test_usershas access of some kind, as does the "OWNER" (which we know from Windows is
sh_dev_test_admins) but what do those letters all mean? The full documentation can be found here, but the critical piece is the following
nfs4_getfaclreturns only the folder name, with no further details. The permissions set on the Windows workstation are respected on the Linux workstation!