Basically the user-related form fields need two extra optional boolean paramaters onlynamed / onlytemp (or something like that) which

• apply an extra validation check to the users on submit, and rejects the appropriate user type
• onlytemp adds an extra auprefix=* parameter to the list=allusers API call for the autocomplete search
• onlynamed skips the autocomplete when the typed text starts with *

(Alternatively, temp/named filtering could be added to the list=allusers API and the form could make use of that. That's nicer in general but has an ugly edge case which is not relevant for the form fields: when iterating through users with onlynamed=1 and no auprefix, you'd end up with a query like SELECT * FROM user WHERE user_name >= $offset AND user_name NOT LIKE '*%' LIMIT $limit and that query will perform catastrophically poorly when iteration reaches to usernames starting with *.)

Change 947359 had a related patch set uploaded (by TsepoThoabala; author: TsepoThoabala):

[mediawiki/core@master] Update user name widgets config to accept or deny temporary user names

https://gerrit.wikimedia.org/r/947359

@TThoabala Thanks for the patch! This seems like good advice, but I notice the patch only does the first one:

In T332030#8740886, @Tgr wrote:

Basically the user-related form fields need two extra optional boolean paramaters onlynamed / onlytemp (or something like that) which

• apply an extra validation check to the users on submit, and rejects the appropriate user type
• onlytemp adds an extra auprefix=* parameter to the list=allusers API call for the autocomplete search
• onlynamed skips the autocomplete when the typed text starts with *

Just wondered if there was a reason behind this?

Moving to the backlog while other work is prioritised