SMB help with groups

[anodos]

Thanks, that makes sense.

Hmm, how do you then explain the Windows confusion?
e.g. when attempting to add group "blah" to the share from Windows, it reverts to user "blah".

When you add an ACL, you need to select "advanced", then select the appropriate "Location" (i.e. DOMAIN or local system), then click "Find Now" to display a full list of all Users and Groups. You should have two "Blahs".

 

[kyp]

One further comment regarding (2). I just created a group "Users" on my freenas server, and it appears as an available group. Unfortunately, there are two "Users" entries without an easy way to differentiate between them. You probably selected the first entry, which is BUILTIN\Users, rather than FREENAS\Users. Since windows looks primarily at SIDs, you're probably okay to use "users", but I still wouldn't trust it.

Hmm, interesting. I only had a single "users" entry - just tested again by creating a group "users".

 

[kyp]

When you add an ACL, you need to select "advanced", then select the appropriate "Location" (i.e. DOMAIN or local system), then click "Find Now" to display a full list of all Users and Groups. You should have two "Blahs".

Correct, I did. But when I selected the group "Blah", after applying, it then reverted to the user "Blah" .... a resolving issue?

 

[anodos]

Correct, I did. But when I selected the group "Blah", after applying, it then reverted to the user "Blah" .... a resolving issue?

Hmm... I guess so. I recall jhixson writing in a git commit that there was some sort of problem with using groups and users with same name.

For reference the code is:

Code:

def smb4_map_groups(client):
  groupmap = client.call('notifier.groupmap_list')
  groups = get_groups(client)
  for g in groups:
	if not (smb4_group_mapped(groupmap, g) or smb4_groupname_is_username(g)):
	  client.call('notifier.groupmap_add', g, g)

The initial git commit regarding it is recorded here, but the code has changed since then. https://github.com/freenas/freenas/commit/6b706ca593199d9fc05ac36a74d4f5a2038570f4

 

[kyp]

I suppose the "or smb4_groupname_is_username(g)" means there's nothing stopping a nt/unix groupmap to be created where group_name = user_name.
But that doesn't mean Windows will handle it well?

UPDATE: Blah, I'm getting inconclusive results now ... I can't reproduce the issue I was having now :)