Submitted by datenimperator on Sat, 02/26/2011 - 03:55
Hi, I've created a user for a virtualmin domain. Afterwards I renamed it useing the webmin "Users and groups" module, and selected "Modify user in other modules" when I saved my changes.
Later I found that the file containing the users plaintext password in /etc/webmin/virtual-server/plainpass/ still contained the old username. That would keep Virtualmin from including the password in "updated user" messages.
Solution: Either have a "rename user" option in virtualmin, or (better) rename the entry when a user is renamed via the webmin module.
Kind regards,
Christian
Status:
Closed (fixed)
Comments
Submitted by Locutus on Sat, 02/26/2011 - 04:23 Comment #1
I don't think this is really a bug. Renaming the user directly in Webmin happens so to speak "behind Virtualmin's back". The Modify user in other modules option probably does not apply to the Virtualmin module, but only to things like Samba, as mentioned in the help text.
To correctly rename a user that's under Virtualmin control, you should do so in Virtualmin -> Edit Mail and FTP Users -> [Username] : Email address. Modifying that will rename all things related to the user, including the Linux user account.
Submitted by datenimperator on Sat, 02/26/2011 - 08:57 Comment #2
You might be right: It's not actually a bug, but more like a feature request.
I simply did not try to put in another username before the @domain in Virtualmin because I suspected that the IMAP login would still be the same. (There was a typo in the username, I didn't want the user to have to misspell his own name during login) A hint would be well in order.
Regarding webmins "modify in other modules": Webmin and Virtualmin are so tightly coupled that it doesn't make sense why such a change wouldn't be picked up by Virtualmin.
Submitted by JamieCameron on Sat, 02/26/2011 - 11:05 Comment #3
I have to agree with Locutus here - if you modify a user via some other method than the Virtualmin UI, it can cause un-expected behavior. I will support this particular case in the next release, but would recommend against this type of change in general ..
Submitted by Issues on Sat, 03/12/2011 - 12:21 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.