Tranquil IT Forum

Good morning,

I can't get my secondary repositories to use HTTPS.
When I change the repository URL, the agent can no longer find it. How can I switch my secondary repositories to full HTTPS?.

THANKS

Hi Clément,

which CA did the certificates deployed to the secondary repositories come from? Is this CA recognized by the WAPT agent?

Regards,

Denis

The repositories contain the certificates of the technicians who have console access in the folder C:\Program Files (x86)\wapt\ssl,
and the certificate of the main server in C:\Program Files (x86)\wapt\ssl\server.

They also have the remote-repo-http package without any special configuration.

Do I need additional certificates?

If you want an HTTPS repository, you need a Public Key Infrastructure (PKI

. You must create a certificate issued by a Certificate Authority (CA) (which you already have, such as OpenSSL, ADCS, or another) for your repositories and your WAPT server.

Then, in `verify_cert` (wapt-get.ini), you must specify your CA.

This will enable valid HTTPS validation.

Thank you for the response. An internal PKI is being considered, so we will revisit this at that time.