Limited package installation capability on certain workstations.

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
guestben321
Messages: 23
Registration: Nov 30, 2021 - 4:38 p.m.

March 8, 2023 - 12:34

Hello,

I know it's possible to restrict user actions to certain workstations (the workstations or their installed certificates).

I was wondering if it's possible to do the same with packages?

For example, if I create a package, is it possible to limit its installation to only certain workstations?

I'm not talking about Self-Service, but rather the use of the console.

Thank you. :)
WAPT Server Enterprise edition, version: 2.6.0.16552
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

March 8, 2023 - 2:19 PM

Hello Benoît,

could you please clarify the use case:
* Is it to prevent human error by an admin
? * Is it due to a licensing issue, confidential data, etc.?

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
guestben321
Messages: 23
Registration: Nov 30, 2021 - 4:38 p.m.

March 8, 2023 - 3:00 PM

Hello Denis,

In the first case. To avoid human error.

Thank you. :)
WAPT Server Enterprise edition, version: 2.6.0.16552
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

March 8, 2023 - 4:54 PM

Hi again Benoit,

there's currently no way to prevent a specific package from being assigned to a machine (as long as the admin has the necessary rights on that machine). As you mentioned, the security model using certificates will prevent deployment if the corresponding certificate isn't installed on the destination machine.

You could potentially use maturity levels, setting a specific maturity level for the package in question and the corresponding machines. The other machines will then no longer see the package.

Alternatively, as a last resort, you could add a check at the beginning of setup.py that verifies if the machine name is in a list or checks against a machine property.

Best regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked