[SOLVED] Self Service Problem

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
wapt.user6325
Messages: 8
Registration: Nov 14, 2022 - 11:26

December 22, 2022 - 1:45 PM

Hello everyone,

I'm using WAPT Discovery.
I'm encountering a problem using Self Service.
According to the documentation, local administrators and members of the "self-service" AD group should have access.

Firstly, the documentation (for Discovery) refers to a "waptself-service" in one place, and then to a "self-service" in another...
=> Which is the correct AD group? Before contacting you, I obviously tried both.

On my end,
- Local admins, with local accounts, have access to Self Service
- Domain accounts, in the local Admin group, also have access.

Local and domain accounts with no admin rights can connect, but the software list is empty.
I've tried:
- Creating a self-service AD ​​group (and waptself-service) to add users: still nothing (even after rebooting, wapt upgrade, etc.)
- Creating the same groups locally on the machine and adding users: same result...

I don't understand where the problem lies.

Thanks in advance. :D

Client on Windows and Server on Debian 11.
WAPT Server version: 2.2.3
WAPT Agent version: 2.2.3.12481
WAPT Setup version: 2.2.3.12481
WAPT Deploy version: 2.2.3.12481
Database status: OK (2.2.6.2)
Last edited by wapt.user6325 on Dec 22, 2022 - 4:17 PM, edited 1 time.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

December 22, 2022 - 3:01 PM

Indeed, there's an error in the documentation; the group is waptselfservice.

This error is not present on the English page : https://www.wapt.fr/en/doc-2.2/wapt-usa ... #discovery
wapt.user6325
Messages: 8
Registration: Nov 14, 2022 - 11:26

December 22, 2022 - 4:11 PM

Thanks so much,
it works now.

Happy holidays to the team,
Alexis
Locked