Image of the empty console

[Dr. Mathieu]

Hello,

For the past few days we've noticed that we can no longer perform any actions in the "Private Repository" tab because it's completely empty! We can see all our workstations and servers, the same for WUA and the other tabs.
We noticed that one of our certificates had expired, but we took the necessary steps to renew it, though nothing has changed.

However, some actions are not possible with one of the certificates we have. Here is the architecture we have implemented for this issue:
- XXX-CA (Root Certificate Authority => All Issuance Policies / All Application Policies)
=> xxx-PKI-SVC (Intermediate Certificate for All Application Policies)
=> WAPT-APP (Intermediate Certificate for All Application Policies)
=> wapt-sign (Certificate for signing packages: Ensures the software came from a software publisher / Protects the software against any modification after its release / Guarantees your identity to a remote computer).

Aside from this, the console is on version 2.5.5.15697 and some workstations have the agent on version 2.6.
We are unsure where to look to resolve the issue because we cannot run updates on the workstations or modify and update the packages.

Thank you for your feedback.
Have a good day

[sfonteneau]

Hello

, I didn't quite understand.

Is the expired certificate a packet signing certificate or the server's HTTPS certificate?

[sfonteneau]

Hello

, I didn't quite understand.

Is the expired certificate a packet signing certificate or the server's HTTPS certificate?

Note: You can switch to version 2.6 to see if anything changes

[Dr. Mathieu]

We plan to release this update in the coming days to see if it resolves the issue.
The certificates may not be related!


Thank you for your feedback.

[Dr. Mathieu]

Hello,

I'm revisiting this topic because we've noticed that while some people in our department have access to the private repository, not everyone does. It's quite strange, and here's why:

- We have an 'admin' account, and we tried logging in with it.
- On my computer, I don't see the private repository and I can't access the packages.
- On another administrator's computer with the same account, they can access it without any problem.
- On a technician's computer with the same account, they can access it without any problem.
- On another technician's computer with the same account, they can't access it. Similarly,

in the Inventory, I no longer see the OU packages. This behavior is really very strange...

Do you have any ideas about this, please?
Have a good day.

[sfonteneau]

The simplest solution on PCs that aren't working:

delete:
C:\Users\%username%\AppData\Roaming\waptconsole

and:
C:\Users\%username%\AppData\Local\waptconsole.


This will remove the waptconsole configuration and allow you to start with a clean configuration.

[Dr. Mathieu]

Great, it worked for viewing private repositories, but do you know why this is happening on the profiles of the affected users?

Another issue related to certificates: on the OUs where we've placed an "Organizational Unit package," it's not possible to build the upload (see screenshot).

Thank you for your feedback.

[htouvet]

You can normally resign it from the private repository

[Dr. Mathieu]

Good morning,

We encounter the same type of error with certificates:

Packet signature verification failed for [...]
None of the following certificates can verify the signature: certificate has expired "WAPT-APP" is not a trusted certificate.

[Dr. Mathieu]

Good morning,

I'm returning to the subject of certificates because it's causing us a lot of problems with building packages on OUs or package groups.
I tried to re-sign a Group package containing software and here's the result:

Packet signature verification failed for Groupe-Global(=2). Signer user-adm.
None of the following certificates can verify the signature:
certificate has expired. "WAPT-APP" is not a trusted certificate.

Thank you for your feedback
Good day