I'm dissappointed of the fact that this feature is not yet implemented.

I just upgraded from web admin edition to web pro edition and re-assigned some of the domains (now subscriptions) to a client who used to have access via admin account. Now I need to keep the "admin" username for this client while changing the admin account name and password so it's not longer accesible by them.

I hope to see this feature in the near future.

Pl introduce it.. Good for security of account.

Best regards

I know Mikhail, but that doesn't solve the problem. The admin user will always be a valid user in the system.

Leonardo, these days you can add additional administrator accounts so you don't have to use admin login any longer. I am in process of switching to Google based authentication and it works reasonably well in such setup.

I think Sergey L has a point to be made.

But I also don't see the harm in having this feature as an option and if the server admin feels the need to change the default 'admin' to another username, that is their choice to make.

I see this feature as a nice to have (if wanted) but not priority.

It's a must have !!! too

have serious doubts this function can really increase server security..... and yet this is one of the most voted and requested feature! Can't you just do it and move on? Is it really that difficult? Also is not just a matter of security, we want to login with OUR name.

+1 for me !

It's a very, very important function for security and it's needed for PCI compliance please imlement it.

It's a must have !!!

It's a very important function, please imlement it.

Team Plesk, please... For PCI compliance a unique/user-definable username is a requirement. This is a very reasonable request from users.

https://www.securitymetrics.com/blog/pci-requirement-8-combatting-weak-passwords-and-usernames

The usual suspect admin user names (admin/sa/root etc) are a common attack vector (especially for distributed attacks) and every half competent admin ought to restrict, disable or delete them. Even better, they present a wonderful opportunity to flag malicious people and direct them to some separate functionality that acts like a black hole to let them spin their wheels without endangering the server in any way.

i wanna change my login name from some random sh*t to a real name

@Sergey L, в вашей компании всё в порядке с клиентоориентированностью? Вам КЛИЕНТ говорит, хочу иметь возможность сменить юзернейм по умолчанию, а вы ему - "We have serious doubts.."? Серьёзно? Нет уж, если введение этой фичи потребует чересчур больших ресурсов, то так и скажите, чего булки мять-то? А если не требует - так почему бы не запланировать в релиз. 328 голосов вам мало? Ну тогда я перестаю думать, что Плеск панель подходящий выбор для хостеров и вебмастеров.

Но это не имеет никакого значения, ведь Plesk International GmbH не волнует мнение даже 328-ми КЛИЕНТОВ, не то что какого-то одного юзера. :)

P.S. Интересно, что бы сделали в подобном случае в CPanel?

Dear Plesk staff,

Here's one angle to look at it from. When we secure our servers - I hope - we all disabled root login and password login, and instead give root privilege to specific users which are further secured with private/public keypairs.
When you spin up a server on the internet, almost immediately you will see bruteforce attempts on root in your fail2ban logs/alerts. As soon as you disable 'root' login, these go away. Some of us will take an extra step by changing the SSH port.

Most of the above steps are 'security by obscurity' in a sense, but they work to thwart a high number of automated attacks running through the internet.

We should enforce passphrases/longer passwords on Plesk by default before worrying about obscuring the admin login username, however the change will most definitely help. It will not be possible for bruteforcers to find the new username unless someone discovers an exploit which allows enumeration of usernames.

Best wishes!

totally agree that people should have a strong password, but i also think just the peace of mind you can give to your customers who dont necessarily know all of the risks as Sergey L has stated are arbitrary to having an "admin" user name. i think the "peace of mind" philosophy goes further than a simple technicality.

Two-Factor, strong password, and making sure every application you are installing on your server has its own security on top of it. leave no risks and you shouldnt have a problem. But again, not everyone follows these practices and would feel better if they were able to customize their own admin names. or at least be able to disable the admin after they have added an additional administrator.

Thanks Mikhail,
That's actually very good point about distinguishing blind brute force attack from a targeted one. Much appreciated!

Fail2ban is great, however it is much safer if a Plesk Console is protected by some obscure login name. This way it is easy to differentiate between brute force attacks and attacks where someone actually paid attention to you and might have stolen some of your login data through other means.

"As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name "

No. A real strong username such as 8t4Xw32lp97BkaQw36VcXp
would add A LOT of security to my account.

PLEASE ALLOW ADMIN TO CHANGE USERNAME. Or at least allow another admin account to be created with such capability. Then we can delete the previous account

This is a respond to That Guy.

Plesk creates a user called admin and uses the password you set when you installed plesk onyx via web interface. What thet should let us do is enable us to rename this user to whatever we want and disable the root user login.

The problem is that because pretty much every single piece of Unix software in existence assumes that the username 'root' exists and that it is the superuser -- mail aliases, various daemons, cron...

So for future reference do not use root when you login to plesk gui use admin :) Hope this clears this up.

Remember set a strong password for the root user in the mean time :) 25+ char long if plesk supports it :D

As Ben has said use google authentication.

or as Anonym said

Go to '' /opt/psa/admin/conf '' then name the " panel.ini.sample " - file to panel.ini and insert:

[login]
systemAdmin = false

im going to do it right now :D

I trust Plesk with our users data and if ur super paranoid dont enable ftp only let users in via gui and set a strong password for ur users. Remember its your job to keep your users data safe with the tools you have. If you dont like it dont use it.

Quite shocking to see such a ignorant response from management of a company that I'm supposed to trust with my and my customers valuable data.

Your argument that it gives a "false sense of security" has no merit. The username plays a critical role in user authentication. With this being so predictable that's 50% of the guess work done, allowing an attack(er) to focus on a single element of the system to attack. Fail2Ban works on the attack(er)'s IP Address. I can quickly and easily get new public IP addresses and set up a brute force attack.

What security risk does this impose?

I fail to see how this would be difficult to implement. It looks like Plesk is just full of lazy developers with little regard to security of their product.

Furthermore Plesk only notifies that a user with "the same username" is logged in. So how am I supposed to know who's alias admin account could be compromised?

Is it going to take an attack on Plesk panels for you guys to get off your lazy aspirations and implement this? Because I'm willing to take it there, try me.