Centrify DirectControl, Centrify Identity Service, Mac Edition, Centrify DirectAudit
Why UID/GID is set to "nobody" when new files created via NFSv4?
Applies to: All versions of Centrify DirectControl on Centos 5.x and RedHat 5.x with Kerberos-enabled NFSv4
Problem: After you have successfully mounted to a NFS server (NetApp filer) using Kerberos-enabled NFSv4, any files you attempt to create on a mounted share results in UID/GID being reverted back to "nobody" even though you have proper read/write permissions to the share.
Note: This used to work fine with NFSv3 - where it was uid/gid based, while NFSv4 is now name based.
Solution: On NFS server, you need to check NetApp settings by executing:
Centrify Corporation does not take any responsibility for the content or availability of this link and it was provided as a courtesy. Customers should contact the vendor if there are any further questions.