Certificate is not trustworthy

[ArthurBrg]

Hello everyone,

I'm having a problem with personal certificates. We tried deploying a certificate for each administrator user. Each administrator created their own certificate and self-signed it. I assigned this certificate to their account and deployed them to some workstations on my network for testing.
However, now, when an administrator adds a package, either from the store or the local repository, their package turns dark gray and displays the message: "The signer of this package is not a trusted certificate."

I was wondering if you know why this problem is occurring?
(I have a theory related to self-signing, but I don't have a CA certificate on my WAPT server.)

Information:
- Version: 2.6.0.16795

Thank you in advance for your answers!

[sfonteneau]

Hello,

in the console, to trust a certificate, you need to add it to the folder mentioned here:

[ArthurBrg]

Hello, thank you for your reply.

Indeed, I didn't have the personal certificates in that folder. However, do I need to create a package to automatically push them to my administrators so they can authorize them all? Or is that unnecessary?

[ArthurBrg]

After further analysis of the problem, I realized I was allowing the certificate to perform actions on all administrator workstations during testing.

So I had the idea to change the path to: "C:\Program Files (x86)\wapt\ssl".

What do you think? In any case, this change solved my problem.

Have a good day!