I created a new user and gave him all privileges, and still when he logged he does not seem to be able to do anything via Wen UI.
What is the trick ?
Thx
Given a user other then 'admin' full admin rights
-
- resolved
- chudak
-
Only the admin user has full control in the WebGUI. I don't think it is possible to have another user with that full functionality. If it is possible, then it is undocumented. What is your use case for needing this?
-
votdev
Added the Label resolved -
admin is hard coded. Volker has asked for PRs if this is needed.
-
-
Multi-tenancy is a really difficult thing in a UI, because of that it has not been implemented from the beginning. For SOHO scenarious it is not necessary.
-
Only the admin user has full control in the WebGUI. I don't think it is possible to have another user with that full functionality. If it is possible, then it is undocumented. What is your use case for needing this?
I use pfsense for years and just trying to compare and see many high level similarities.
Although I don't have a use case, and think users can "live" with hard-coded "admin", it'd be much better to be able to allow another user as well, say for security purposes have full access, so "admin" alias is not used at all
Makes sense ?
-
Makes sense to me if all user actions were logged by username. Then you could tell who did what or who broke what
-
-
Makes sense to me if all user actions were logged by username. Then you could tell who did what or who broke what
Say somebody broke thru your firewall and starts scanning services. Why let him know that OMV default user is "admin"??
-
Why let him know that OMV default user is "admin"??
They know you have a "root" account too.
-
They know you have a "root" account too.
Same argument, why ? Allow OMV owner decide and disable root and admin users and use a new user(s) as admin !
Illogical ?
-
-
Same argument, why ? Allow OMV owner decide and disable root and admin users and use a new user(s) as admin !
Illogical ?You can disable root ssh access from the omv web interface. The admin user really doesn't bother me because I don't expose the the web interface to the internet. If an attacker was inside you network, you have big problems. Use a very strong password for the admin user. Problem solved. Lots of things (microsoft sql server with sa for example) use a hard coded super user name.
-
You can disable root ssh access from the omv web interface. The admin user really doesn't bother me because I don't expose the the web interface to the internet. If an attacker was inside you network, you have big problems. Use a very strong password for the admin user. Problem solved. Lots of things (microsoft sql server with sa for example) use a hard coded super user name.
and they get hacked !!!
-
While knowing the username helps, the password is most important. If you have a 24 character password, how long is going to take to brute force that even if you know the username??
-
-
But assuming it's a trivial change in design - why not ?
What makes you think this change in design would be trivial?
You are aware that OMV is open source, right? Feel free to make whatever changes you want.
-
What makes you think this change in design would be trivial?
You are aware that OMV is open source, right? Feel free to make whatever changes you want.
I said "assuming" and ack and copy on the second point !
-
-
One reason might be that some of the users are confused already about user name to use for GUI login vs. ssh login.
Another layer of complexity for giving support.
BTW: did you notice that it is very common to use predictable user names for all sorts of applications even in professional environment. Think of e-mail address or user names that are composed by x-letters of first name + y-letters of last name. Strong password is really the key.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!