Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerStore Configuring Multiprotocol File Sharing

Access policies for NFS, SMB, and FTP

In a multiprotocol environment, the storage system uses file system access policies to manage user access control of its file systems. There are two kinds of security, UNIX and Windows.

For UNIX security authentication, the credential is built from the UNIX Directory Services (UDS) except for nonsecure NFS access, where the credentials are provided by the host client. User rights are determined from the mode bits and NFSv4 ACL. The user and group identifiers (UID and GID, respectively) are used for identification. There are no privileges that are associated with UNIX security.

For Windows security authentication, the credentials are built from the Windows domain controller (DC) and Local Group Database (LGDB) of the SMB server. User rights are determined from the SMB ACLs. The Security Identifier (SID) is used for identification. Privileges that are associated with Windows security, such as TakeOwnership, Backup, and Restore, are granted by the LGDB or group policy object (GPO) of the SMB server.

The following table describes the access policies that define what security is used by which protocols:

Table 1. Access policiesColumn one lists access policies, column two describes the properties of the policy.
Access policy Description
Native (default)
  • Each protocol manages access with its native security.
  • Security for NFS shares uses the UNIX credential that is associated with the request to check the NFSv3 UNIX mode bits or NFSv4 ACL. The access is then granted or denied.
  • Security for SMB shares uses the Windows credential that is associated with the request to check the SMB ACL. The access is then granted or denied.
  • NFSv3 UNIX mode bits and NFSv4 ACL permission changes are synchronized to each other.
  • There is no synchronization between the UNIX and Windows permissions.
Windows
  • Secures file level access for Windows and UNIX using Windows security.
  • Uses a Windows credential to check the SMB ACL.
  • An SMB ACL conversion determines permissions for newly created files. SMB ACL permission changes are synchronized to the NFSv3 UNIX mode bits or NFSv4 ACL.
  • NFSv3 mode bits and NFSv4 ACL permission changes are denied.
UNIX
  • Secures file level access for Windows and UNIX using UNIX security.
  • Upon request for SMB access, the UNIX credential that is built from the local files or UDS is used to check the NFSv3 mode bits or NFSv4 ACL for permissions.
  • The UMASK determines permissions for newly created files.
  • NFSv3 UNIX mode bits or NFSv4 ACL permission changes are synchronized to the SMB ACL.
  • SMB ACL permission changes are allowed in order to avoid causing disruption, but these permissions are not maintained.

For FTP, authentication with Windows or UNIX depends on the username format that is used when authenticating to the NAS server. If Windows authentication is used, FTP access control is similar to that for SMB; otherwise, authentication is similar to authentication for NFS. FTP and SFTP clients are authenticated when they connect to the NAS server. It could be an SMB authentication (when the format of the username is domain\user or user@domain) or a UNIX authentication (for the other formats of a single username). The Windows DC of the domain that is defined in the NAS server ensures the SMB authentication. The NAS server ensures the UNIX authentication according to the encrypted password stored in either a remote LDAP server, a remote NIS server, or in the local passwd file of the NAS server.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\