IMO, this is a very important feature and should be implemented ASAP.
system users should always be automatically prefixed OR suffixed so that they become unique.
The users should be namespaced, otherwise, it gets hard for customers to find something meaningful that's still not occupied by somebody else, they need to poke around and usually become frustrated with usernames being occupied
Consider this:
Our customers will be automatically provisioned and they will get automatically assigned system/ftp user which has the following name convention: admin_{domian_name} (this is a suffix, but it could be a prefix as well). For example, domain1.com get's admin_domain1_com user automatically created. The problem here is that once the domain is created, the customer will be able to create user with any username, so they will be able to eventually crate user with username admin_domain2_com, thus preventing our provisioning system to use admin_domain2_com once domain2.com get's provisioned with us on the same server (essentially stealing the username).
In order for you guys to make unbreakable change, you can implement functionality that will allow for to turn on/off the system user unique prefix/suffix, based on the domain name. This way you can have both the original behavior and the new one, thus you'll be able to support both use cases.
Ivo
IMO, this is a very important feature and should be implemented ASAP.
system users should always be automatically prefixed OR suffixed so that they become unique.
The users should be namespaced, otherwise, it gets hard for customers to find something meaningful that's still not occupied by somebody else, they need to poke around and usually become frustrated with usernames being occupied
Consider this:
Our customers will be automatically provisioned and they will get automatically assigned system/ftp user which has the following name convention: admin_{domian_name} (this is a suffix, but it could be a prefix as well). For example, domain1.com get's admin_domain1_com user automatically created. The problem here is that once the domain is created, the customer will be able to create user with any username, so they will be able to eventually crate user with username admin_domain2_com, thus preventing our provisioning system to use admin_domain2_com once domain2.com get's provisioned with us on the same server (essentially stealing the username).
In order for you guys to make unbreakable change, you can implement functionality that will allow for to turn on/off the system user unique prefix/suffix, based on the domain name. This way you can have both the original behavior and the new one, thus you'll be able to support both use cases.