Hello,
Due to an accidental error, the "admin" account's privileges were removed from the Tools > User and Rights Management in the WAPT console (Windows).
Since then, we have been unable to administer our workstations. The WAPT console's admin options, such as User and Rights Management, Generate a WAPT Agent , and Generate a Certificate, are grayed out.
We ran the script /opt/wapt/waptserver/scripts/postconf.sh on the WAPT server (version 2.2), but resetting the admin password (without changing the certificates) does not resolve the issue.
Is there a solution to restore the "admin" account's privileges?
Have a good day.
WAPT version installed: WAPT 2.2 Enterprise.
Server OS: CentOS 7.
Administration machine OS: Windows 10.
[SOLVED] Admin ACL Issue
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Hello,
I finally solved my problem by renaming the "admin" account on the WAPT server by adding the `wapt_user` to `/opt/wapt/conf/waptserver.ini` (example: `wapt_user = totoadmin`).
Once the server restarted, logging into the WAPT console with the newly renamed "admin" account restored my administrative privileges.
Have a good evening.
WAPT version installed: WAPT 2.2 Enterprise.
Server OS: CentOS 7.
Administration machine OS: Windows 10.
I finally solved my problem by renaming the "admin" account on the WAPT server by adding the `wapt_user` to `/opt/wapt/conf/waptserver.ini` (example: `wapt_user = totoadmin`).
Once the server restarted, logging into the WAPT console with the newly renamed "admin" account restored my administrative privileges.
Have a good evening.
WAPT version installed: WAPT 2.2 Enterprise.
Server OS: CentOS 7.
Administration machine OS: Windows 10.
