Tranquil IT Forum

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

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?

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

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