I found that TrueNAS usernames, user groups, and datasets are not allowed to be named in Chinese, only in English, which greatly affects the user experience. For datasets, I can accept using only English, but not Chinese as usernames and user group names, which greatly affects enterprise workflows
Datasets are very limited in characterset and based on the filesystem (ZFS) see manpage. That won’t change. Usernames and group names should allow UTF8, but it looks like the UI might be over-strict in validation.
So may it be expected that the GUI will relax to allow UTF8 user/group names, or should interested users open a Feature Request?
No. It was a mistake on my part. Currently a bug actually in backend validation in master, but I’ll raise question of allowing UTF8 for local accounts minus leading hyphen (-) and trailing dollar sign ($) which may definitely break some things.
Generally posix specifications are that usernames should conform with the portable filename character set
That said, if you use AD or LDAP then UTF8 account names carry over to TrueNAS. Enterprise users honestly shouldn’t be heavily using local accounts on TrueNAS anyway.
1 Like
The section addressing Unicode user names published by Debian states this:
It is generally considered a bad idea to use unicode user names. Too many software tools interact with User Names without proper care. The very least requirement to allow Unicode User Names would be to do Normalization at least for comparision, duplicate detection and sorting.
This is not a rule of course, instead it gives a forewarning on the type of issues one can expect if using unicode user names.
Yeah, I thought about it some more (still drinking morning coffee) and we really can’t expose full UTF8 here. Too much risk of breakage. As mentioned, OP should be using some directory service anyway.
For example:
ACME\блин:*:100011617:100000514::/var/empty:/bin/sh
AD providing unicode username. If you’re in enterprise and creating local NAS user accounts for your users then you’re basically doing the wrong thing.
1 Like
I can accept the dataset, as it is not publicly available. I hope that the publicly available fields can accommodate as many characters as possible. If it’s just a UI issue, then I should study it carefully. Thank you for your answer~
I also hope very much
If I don’t use a local account, how can I use TrueNAS to create dedicated accounts other than the local account to support the operation and use of SMB?
We mainly use SMB services on TrueNAS, but I need to create an account for each department (without using AD functionality), so I create usernames and POSIX permissions on the TrueNAS system to restrict access to SMB folders. Is there any other way to create dedicated accounts on TrueNAS to meet SMB sharing needs?