Restrict user access

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
Chernobyl
Messages: 2
Registration: Oct 23, 2017 - 4:21 p.m.

October 23, 2017 - 4:47 PM

Good morning,

I am currently working on setting up a WAPT pilot which consists of setting up a multi-site and multi-warehouse architecture; we will have several agencies each with several warehouses.
Ideally, we would like to have a private repository; which can only be manipulated by system admins to manage critical deployments, and a public one; from which regular users could install non-critical packages themselves.
The web server used for WAPT servers is IIS, and we are working on an Active Directory domain.
  • 1
After this far too long exhibition ;) The question we are asking is whether there is a trick to control access rights to repositories from IIS or AD to prevent users from touching critical packages?
  • 2
idea: Alternative: Is it possible to modify the client's web interface (or are there modules available) to hide certain repositories, if not to block access to them?
High
User avatar
agauvrit
WAPT Expert
Messages: 238
Registration: Nov 17, 2016 - 10:25
Location: Nantes
Contact :
Contact agauvrit

October 24, 2017 - 3:05 PM

Hello,

These features are not available in the open-source version of WAPT.

Please contact our sales support for more information about the Enterprise version of WAPT.

Sincerely,

Alexandre
High
Chernobyl
Messages: 2
Registration: Oct 23, 2017 - 4:21 p.m.

October 25, 2017 - 09:34

Ideally, we'd like to make do with what we have in place.
Thanks anyway.
High
Locked

Return to "WAPT usage (Console, Agent) / WAPT usage (Console, Agent)"


  • To go further with WAPT