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
[SOLVED] Private repository display issue since version 2.6
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
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
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
Hi
, same problem on a Debian server...
, same problem on a Debian server...
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
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
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
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
Hello,
great, thanks Denis for the info.
Now we just have to wait.
great, thanks Denis for the info.
Now we just have to wait.
