Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
Thanks for the quick response. I did see the protocols for NFS, CIFS, etc at the SVM level (Data Protocols). At the volume level, it has to be specified with "Mixed" security style if one chooses to have both NFS & CIFS on that volume?
Security style and access protocol are completely different things.
There are 3 different security styles:
- Unix : file permissions are based on Unix permissions (rwx) and can only be modify by Unix clients
- NTFS: file permissions are based on Windows ACL and can only be modify by Windows clients
- Mixed: filer permissions are based on Unix permission or on Windows ACL (but not at the same time). If the last client who change permission are a Unix client, permission will be Unix. If the last client is a Windows client, permission will be NTFS.
For example, a Unix security style volume can be accessed by NFS and CIFS but files permissions will be only Unix. Even a Windows client will only view 3 differents permissions (Read/Write/Execute).
Personaly, I'm trying not to use Mixed security style. If you put a lot of ACL on a folder and then, a Unix client use the "chmod" command, all the ACL will be lost.