Multi-depot

[hasop]

Hello,

The documentation (https://www.wapt.fr/fr/doc/Multi-depot/index.html) indicates that it's possible to create a multi-repository to, for example, differentiate between free and licensed software.

However, I don't see the configuration details for making only the free software repository visible to the user. Is there any additional documentation available?

Thank you in advance.

[agauvrit]

Good morning,

We are currently rewriting the documentation; the updated version is here: https://www.wapt.fr/fr/doc-1.5/Replicat ... index.html

It is possible to differentiate between the deposits:

• General software repository
• Microsoft Software Repository
• Adobe Software Repository
• Software deposit under other licenses (AutoDesk/Dassault Systems/etc.)
• etc..

Adding these repositories to agent configurations is easily done using a WAPT package, following the example of this package: https://store.wapt.fr/package_details?p ... 6_all.wapt

Package visibility filtering by user group, based on Active Directory security groups, is only available in version Enterprise from WAPT.

Sincerely,

Alexander

[hasop]

Thank you for your feedback.

However, in addition to the functionality you describe (which could be of interest to us if the application test is successful), it seems useful to be able to separate a software repository that the user cannot see, regardless of their access rights (for example, all the tools deployed by default on their machine), from those they can see in the self-service area.

Indeed, I don't find it logical that a user can view/delete packages deployed by default, even if they are present on their machine. Essentially, they have the right to have them, but this should be transparent to them.

Will your system, based on the Enterprise edition of Active Directory, allow this functionality, or is it something else?

In the documentation you mentioned, there doesn't seem to be any further information on the repository's visibility in the self-service area. Am I mistaken?

[sfonteneau]

One of the features in the open-source version is the restricted section.

https://github.com/tranquilit/WAPT/blob ... t.html#L56

If a package is a "restricted" type package, it won't appear in the agent's web service. However, this is a global setting.

In the enterprise version, you can define software access based on Active Directory user groups.

For example, you can define that users in the accounting group will have access to the tis-msoffice and tis-adobecs6 packages.

The user will then be able to install or uninstall the software!

Note: If someone uninstalls software that is dependent on the package, the software will reappear, since the dependency will no longer be present! The WAPT agent will then try to resolve the missing dependency!

[hasop]

These two features are indeed very interesting.

One last thing: To make the package invisible, you need to add "section: restricted" to the control file, right?
Is it possible to do this from the interface (make a package imported from the internet "restricted" without having to edit it)?

[sfonteneau]

These two features are indeed very interesting.

One last thing: To make the package invisible, you need to put "section: restricted" in the control file, right?

Yes

Is it possible to do this from the interface (make a package imported from the Internet "restricted" without having to edit it)?

No

[hasop]

I think it's not that easy technically, but it could be interesting to be able to edit certain package properties directly from the interface (name, section, etc.).

I have all my answers, thank you very much!

[sfonteneau]

I think that technically it's not that easy, but it could be interesting to be able to edit certain package properties directly from the interface (name, section, ...)

Not planned for the moment