Tranquil IT Forum

Hello,

My problem is as follows: I want to "offload" package development and administration from the WAPT console to client machines. However, these machines are blocked from all modification actions with the message "private key does not exist".

I initially thought it was a problem related to my custom WAPT agent where the key might have been incorrectly entered, but no.
I then realized that the custom WAPT agent only accepts the .crt key, necessary for using packages, but not the .pem key for development and creation.
By manually copying the .pem key, I was then able to use the administration options of the WAPT console.

Is this normal? Is there a way to "automate" this?

Best regards,

Luc

Hello,
Yes, this behavior is perfectly normal. Only the public key ".crt" is copied into the WAPT agent.

The private key ".pem" should not be widely distributed because it is used to sign packets.

If you need it, you must copy it manually.

Frédéric Bonnier