File ownership mismatch.

[dot.dot]

Hello.
I'm sure I'm doing something wrong but this is the case, the same file shows 3 distinct ownerships.

I enrolled TrueNas on my AD DC, and can see the users/groups using:

Code:

wbinfo -u
wbinfo -g

I log into a linux machine using an account: local (this account is the local admin)
I then mount the samba share located on my TrueNas using one of the AD DC users DOMAIN/user1 and can create a file.
But the ownership for the files is not what I expect them to be, nor reported in a consistent manner:

Via the client GUI root owns the file (I logged in as local, not root):

Via CLI, navigating to the mount point using gvfs the file is owned by local:

Then Shell on the TrueNas machine itself, itis owned by DOMAIN/user1:

I know I must be doing something wrong/missed a step somewhere, can someone point me at the right direction?
Thanks!

 

[Johnny Fartpants]

Try adding the AD username in your mount command like this:

sudo mount.cifs -v //yourserver/stuff/ -o username=ADusername,domain=yourdomain /yourmountpoint.

 

[dot.dot]

Thanks for the reply.

I went ahead and added automount via pam whenever a domain user logs in. but i still have some issues.The GUI still reports the ownership as being the user that is logged in at the moment, not the one who created the file, on windows it works straight away.
Perhaps linux is reporting the owner of the mount,rather than the owner of the file as per truenas?

The CLI on Kubuntu at least matches the GUI now:

And on Truenas it matches what i was seeing on Windows:

I learned a bit, but not how to get around this :/

 

[Johnny Fartpants]

How are your permissions setup on the share?

 

[anodos]

gvfs may have improper handling for cases where share doesn't have SMB1 unix extensions enabled. For that matter, if your Linux client is not joined to AD, it can't convert the SIDs it receives over the wire to uids / gids and so just shows current user as owner.

 

[dot.dot]

Many thanks for your help, it nudged mein the right direction

I am authenticating my users against an AD DC.

My solution ended up being this:
Mount the share as nfs instead of cifs (i am mounting on pam_mount_conf.xml)(cifs on linux still does not work well, but i am not using it).
I had to also fix the idmap settings so that both TrueNas and the clients match the AD DC. (anodos you ended up helping me on that too!)

So my first suspicion that I was doing something wrong holds true.
(But perhaps the idmap settings should be enabled by default, as it seems to me that is the way you'd want it to be all the time? )