AD users and grups are mixed up in GUI

[CableGuy]

TrueNAS Core FreeBSD 12.2-RELEASE-p10 b26f74b5984
Hardware: SM SuperStorage 2029P-E1CR24H

I added an external AD to TrueNAS
truenas# midclt call activedirectory.domain_info | jq
works just fine.
wbinfo -u and wbinfo -g show the correct users and groups like:
MYDOMAIN\myuser
MYDOMAIN\mygroup

I would like to add an NFS share for each user or for a certain group. Where each user has their own directory with 4 GB of maximum space.
In the Web GUI I go to:
Sharing > Unix Shares (NFS) > ADD > ADVANCED OPTIONS
Here i choose a pool
Under: Access > Maproot User
I click on the "down arrow", here I get a list of all users and groups mixed up into one list.
And the list is incomplete, it does not show users or groups that start with "g to z".
It stops after: MYDOMAIN\frank
This is the same for Maproot User/Group and Mappall Group/User.
I suspect this is not correct. I expect only to see users under Maproot User and only groups under Maproot Group.
I have around 60 users and 30 groups.

What can I do?

 

[CableGuy]

Global parameters
[global]
aio max threads = 2
allow trusted domains = No
bind interfaces only = Yes
client ldap sasl wrapping = seal
disable spoolss = Yes
dns proxy = No
domain master = No
enable web service discovery = Yes
kerberos method = secrets and keytab
kernel change notify = No
load printers = No
local master = No
logging = file
max log size = 5120
nsupdate command = /usr/local/bin/samba-nsupdate -g
preferred master = No
realm = CANTTELL.MYDOMAIN
registry shares = Yes
restrict anonymous = 2
security = ADS
server role = member server
server string = TrueNAS Server
template shell = /bin/sh
unix extensions = No
winbind cache time = 7200
winbind enum groups = Yes
winbind enum users = Yes
winbind max domain connections = 10
workgroup = MYDOMAIN

 

[anodos]

Depending on winbindd idmap backend, ID_TYPE_BOTH may be used, in which case there are user and group objects for both entries. In SCALE (and possibly) 13 I reworked some aspects of this to avoid a POLA violation but it's not going to be backported to 12.

 

[CableGuy]

I figured out that I just could just enter the credentials manually, instead of using the drop-down menu.

But now I got another problem:
I have "Enable NFSv4" set to On.
But it does not seem to be running. Just version 2 and 3 seem to be on...
Restarting the NFS service does not change anything.

rpcinfo MY_TRUENAS_IP | egrep "service|nfs"
program version netid address service owner
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100003 2 tcp6 ::.8.1 nfs superuser
100003 3 tcp6 ::.8.1 nfs superuser