Tranquil IT Forum

I'm going to share a problem we're having.
Here's what I configured: a self-service portal (Infra_Rep02) as follows:
I specified the AD group "INFRA_GG" to which the AD account mateus.junior belongs.
And on the self-service portal, I only defined a few packages for this self-service!
Here's a screenshot of the self-service configuration: http://snpy.in/Yu2ssu
Here's a screenshot of the AD group: http://snpy.in/U0AD2g
Here's a screenshot of the client machine: http://snpy.in/kuFToW

When I go to mateus.junior's client machine and access his self-service portal, I notice that he has all the packages, instead of just the limited packages as configured.
Here's a screenshot: http://snpy.in/1iOTzv

Is the user an administrator on their machine? https://www.wapt.fr/fr/doc/wapt-usage-a ... lf-service
Is the user a member of a group named waptselfservice? https://www.wapt.fr/fr/doc/wapt-usage-a ... inistrator

sfonteneau wrote: ↑June 22, 2022 - 11:04 AM Is the user an administrator on their machine? https://www.wapt.fr/fr/doc/wapt-usage-a ... lf-service
Is the user a member of a group named waptselfservice? https://www.wapt.fr/fr/doc/wapt-usage-a ... inistrator

Hello, yes, the user is also a local administrator of their machine
I just disabled the packages for local administrators, according to the tutorial
http://snpy.in/8O93Vl
I am modifying the wapt-get.ini file: http://snpy.in/dEJn7I
I'm creating a new group in Active Directory, including: waptselfservice: http://snpy.in/Py7cOY
I modified the selfservice which now points to the new waptselfservice group: http://snpy.in/6gQBU7
I updated the PC in the WAPT console, but unfortunately, I still see all the packages on the machine!

I didn't quite understand you.

You should n't create a waptselfservice group (users who are members of this group can see all the packages).

sfonteneau wrote: ↑June 22, 2022 - 12:23 I didn't quite understand you.

You should n't create a waptselfservice group (users who are members of this group can see all the packages).

OK, I just changed the group name to infraselfservice: http://snpy.in/9ew4dJ
I created a new infraselfservice group in the AD: http://snpy.in/KLEWtz

juniormateus wrote: ↑June 22, 2022 - 12:38

sfonteneau wrote: ↑June 22, 2022 - 12:23 I didn't quite understand you.

You should n't create a waptselfservice group (users who are members of this group can see all the packages).

OK, I just changed the group name to infraselfservice: http://snpy.in/9ew4dJ
I created a new infraselfservice group in the AD: http://snpy.in/KLEWtz

But the problem persists; this customer continues to see everything!

There's one last subtlety I forgot.

Is your user a member of domain admins?

Administrators can see all packages even with the waptservice_admin_filter condition.

sfonteneau wrote: ↑June 22, 2022 - 1:04 PM There's one last subtlety I forgot.

Is your user a member of domain admins?

Administrators can see all packages even despite the waptservice_admin_filter condition

I'm going to test that

juniormateus wrote: ↑June 22, 2022 - 1:10 PM

sfonteneau wrote: ↑June 22, 2022 - 1:04 PM There's one last subtlety I forgot.

Is your user a member of domain admins?

Administrators can see all packages even despite the waptservice_admin_filter condition

I'm going to test that

Hi, I just tested it on a user who isn't a member of domain admins, and the problem is the same; they can see all the packages

I just noticed a small typo in the documentation:

the parameter is correct and not I'll correct

then restart the service