System / Root privileges

Status
Not open for further replies.

rameshj

Free User
Joined
Feb 8, 2023
Messages
5
Reaction score
1
I currently sign into mgmt console with user id - admin. This id does not have any user associated with it. I get an error - You need to assign an extension user System / Root privileges. If the current 3CX administrator does not have an extension you need to create one for him. Then go to the user account, click on the Rights tab and select System Owner role in the Group Membership section.

What are my option?

I prefer to add an extension for this id but I do not see it in the user list. How do I do that and associate this id with a user/extension and make hime the system owner. Or do I need to create a new user with different id/email and add ext and make it the system user? If so, what happens to this ID?

Thanks
 
The system owner role is new in update 6. Check the blog posts about u6. You can just create a new extension and assign the role, or use an existing extension. It’s unrelated to the management console user.
 
The system owner role is new in update 6. Check the blog posts about u6. You can just create a new extension and assign the role, or use an existing extension. It’s unrelated to the management console user.
Perfect. Changed the role of a current user. Problem Solved. thanks for the quick response.
 
Hi!
On February my 3CX on AWS crashed without a reason. The server was responsive but 3CX services were unable to go up.
So I was forced to restore the backup.
I created a new AWS instance with the 3CX template, copied the backup file to the new server and started the restore process.
Everything was fine, 3CX was up but when I reached the mgmt console using Admin, a red error that I've never seen before apeared: "You need to assign an extension user System / Root privileges. If the current 3CX administrator does not have an extension you need to create one for him. Then go to the user account, click on the Rights tab and select System Owner role in the Group Membership section."
Since I did not know exactly what it was, I started to seek information before doing anything. After one day I was locked out "Root Rights", so I basically had no right to create, delete or edit users.
I tried to edit extension 10000 and change the DEFAULT group's right to system owner but I was already out.
I created a new AWS instance, restored the backup again and this time I've noticed a message saying that extension 10000 was going to be assigned System Ownership. So when I logged in using extension 10000 I was able to edit users. When using Admin, the error message was the same.
Today I was trying to create a new user and .... surprise... Locked out again.
My questions are, what am I doing wrong? Why after the restore, extension 10000 seems to be the owner and after that it loses it? Is there a workaround to solve this without restoring a backup?
If someone could help me with the details on how this is done the right way and what are my options after getting locked out I'll be really thankful.
 
The System Owner role was new and required in update 6. You should have also received an email from 3CX around February 9 as they emailed all our clients. The banner should stay until the role is assigned.

Can't speak to whatever else is going on. We created a new extension, assigned the role, and created a new group for that extension. It shouldn't self-assign. Also the system owner role is for that extension managing the web client admin area, and not the management portal, they are different.
 
Ok. Thanks for the reply.
So, where exactly should I go to assign the System owner role to extension 10000? Because after restoring the server I tried to access https://<FQDN>.my3cx.com.br:5001/ using Admin, but the message was already there and after 1 day I am again unable to manage any user. But right after restore when I used 10000's extension credentials, there was no message and I was able to manage users as before. That's why I thought the rights were just assigned directly to extension10000 by the system (which in my opinion should be the case).
Once I'm stuck again, I'm probably doing something wrong by trying to grant access on the wrong place.
Could you point me the right direction please?
Thanks again for your kindness!
 
What we did was:
  • Log into management console (not web client)
  • Create System Owner extension
  • Create System Owner Group group with System Owner as a member (in one step, if that matters)
  • Remove System Owner from DEFAULT group
  • Set System Owner ext as the System Owner role of the System Owner Group
You can of course use an existing extension if desired.

Per the above 3CX blog post, "If the current 3CX administrator does not have an extension you need to create one. Then, in the Management Console, go to the User account, click on the Rights tab and select System Owner role in the Group Membership section."

The system owner extension can't log in to the management portal and vice versa, they are separate.

What is the specific message you're seeing? If it's about being locked out that sounds like your IP is being blacklisted. Add your IP as an Allow entry, and/or review the 3CX logs to figure out why...since otherwise it will keep happening.
 
  • Log into management console (not web client) - OK
  • Create System Owner extension - Already there - ext.10000
  • Create System Owner Group group with System Owner as a member (in one step, if that matters) - Group Root created but since Admin account (no extension) is MANAGER, I can't assign System Owner os System Administrator to the group.

    After that neither Admin or 10000 is able to manage group roles above MANAGER.
    There is no user in the system with System Administration or System Ownership that can log into the MGMT console.
    That's why I was talking about being locked out. Any user will access MGMT console but with MANAGER RIGHTS. With that I'm sure I'm not blacklisted.
    Somehow, after last restore on AWS on a new server, I was able to manage users with extension 10000 over MGMT console. 1 or 2 days passed by and now ext.10000 is only a MANAGER.
    I'll try to restore again and follow your recipe.
    I hope it works.
    Just for the record, I'm using Version 18.0 Update 7 (Build 312). It looks like a bug. Just to be safe the system should ask during the restore process or over a new installation which extension will be the chosen one and automatically assugn it to the System Owners group.
 
How do i regain access to management console as i did not have linked any email to my admin user but i do have a user extension with rights of System owner however upon loggin with the extension credentials i am being diverted to https://myurl.com/#/people. please assist what do i do
 
How do i regain access to management console as i did not have linked any email to my admin user but i do have a user extension with rights of System owner however upon loggin with the extension credentials i am being diverted to https://myurl.com/#/people. please assist what do i do
If you updated to the v20 beta/RC there is no management console. System Owner will have an Admin page in the web client.
 
If you updated to the v20 beta/RC there is no management console. System Owner will have an Admin page in the web client.
How do i revert back i do not like this at all i already tried restoring no luck so far
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet