Tranquil IT Forum

Hello,

I've noticed that since upgrading WAPT from version 2.5.5.15691 to version 2.6.016714, my private repository is empty when I open my console.
I have to click "refresh available packages" to see them appear.

Is this normal?

For your information, my server is a Windows Server 2022 with WAPT Enterprise version 2.6.0.16714.

Thank you,
Christophe

Hi
, same problem on a Debian server...

Hi Thomas and Christophe,

we've found the problem. It will be fixed in the next version.

The issue stems from the loading of the OU package display in the Active Directory tree view of the inventory tab. This loading occurs a little too early, before the authorized certificates are loaded in the console. In WAPT version 2.6, the private repository tab only displays packages that are valid according to the certificates authorized in the console. Since the certificates are loaded after the OU packages are displayed, the "private repository" tab, by default, doesn't display any packages (because the signatures are not valid according to the already loaded certificates). Refreshing the tab forces the certificates to be reloaded and revalidated, which makes the packages visible again.

We're going to do two things: fix this load order issue, and then add a warning if packages aren't visible due to an unrecognized certificate on an admin's console (this happens in large organizations with delegated access rights, and some packages are only applicable to a subset of the WAPT server's management scope, and are therefore signed with a key valid only within that subset).

We'll keep you updated on the release of the fix.

Sincerely,

Denis

Hello,

great, thanks Denis for the info.

Now we just have to wait.

It's all good, thanks