To support the NFS protocol, HCP supports certain POSIX metadata for objects. This metadata includes the POSIX user ID (UID) of the object owner, the POSIX group ID (GID) of the owning group, and the POSIX permissions.
- POSIX object ownership is different from object ownership in HCP. The owner UID is not related to either HCP user accounts or Active Directory user accounts.
- POSIX permissions are different from HCP data access permissions and access control lists. They affect the operations that clients can perform only through the CIFS and NFS protocols.
POSIX UIDs and GIDs are visible through the HTTP, WebDAV, CIFS, and NFS protocols. POSIX permissions are visible through the WebDAV and NFS protocols. They map to CIFS permissions, which are visible through the CIFS protocol.
For objects stored through NFS, the POSIX UID and GID are determined by the current NFS user. Objects stored through other protocols do not have an explicit UID or GID. Instead, when you use NFS to view these properties for such an object, you see the default UID and GID currently specified in the NFS protocol configuration for the namespace that contains the object.
When you create a namespace, the default UID and GID in the NFS protocol configuration are both set to 0 (zero). You can change these settings at any time.
POSIX permissions for objects, directories, and symbolic links stored through NFS are determined by the client. POSIX permissions for objects stored through other protocols are always 555. POSIX permissions for directories and symbolic links stored through other protocols are always 777.