Win to unix name mapping

[lyric nymph]

While doing win to unix name mapping for a unix security style share, for a unix security style cifs share.
Do I need to be worried about the uid and gid of the unix user I create?

[ashen sand]

The uid should be available to the svm. Usually, in an AD environment with Linux, i see sssd in play that is pointed to AD

The Netapp svm would need an LDAP client created (bind-as-cifs-server for easier config) and it will use that to collect the uid/gid info

[lyric nymph]

There is no ldap or nis client so does that change anything.

[ashen sand]

You need to create one

ldap client create -vserver xxx …

Then apply it to the svm

[tawdry bloom]

what do you mean by " for a unix security style share, for a unix security style cifs share"?
what security style is your volume (or qtree)? and what protocol are you using to access (CIFS or NFS)?

but in general yes, you need to be aware of the UID and GID, because that is what is being stored in the volume (if the security style is UNIX) or presented to the client (if the protocol is NFS)

[lyric nymph]

Volume and qtree are both unix security style and users are accessing share using CIFS protocols on their local machine, I was just curious if I can use any random uid and gid or it has to be specific and what are the rules governing that.

[tawdry bloom]

there are no "rules" per se. You can map all windows users to a single UID if that is what you want. But then if you access the files via NFS, the permissions might not be what your users are expecting and they might have trouble reading/writing the files

[sudden sigil]

Whatever you do, try not to use the "mixed" security style on the volume/qtree... it is just a very sure way to constant issues if you or your users do not know that they are doing 😉