Hello,
I'm setting up a WAPT server and I've ended up with a lot of certificates scattered everywhere...
I have them in:
- c:\wapt\private: a random name with a .crt file and the same one with a .pem file
- c:\wapt\ssl: administrator.crt
- c:\private: administrator.pem and administrator.crt
I don't understand these certificates at all.
Administrator.pem and .cert were created during installation, but the rest...
Could someone please explain the differences and what I should keep/delete?
Thank you in advance.
[RESOLVED] Certificates
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
in Wapt you can recognize private keys as .pem files and public keys as .crt files.
In C:\private you have your private and public key pairs which allow you to sign packets (mykey.pem and mykey.crt).
In c:\wapt\ssl you only have mykey.crt, this tells your agent that it accepts all Wapt packets from the mykey.pem key.
As for the files in c:\wapt\private, they are completely internal to Wapt; you don't need them.
For more information, see: https://www.wapt.fr/fr/doc/wapt-securit ... urn-states.
Regarding the certificate, which is potentially located in c:\wapt\wapt\ssl\server, see:
https://www.wapt.fr/fr/doc/wapt-securit ... apt-agents
in Wapt you can recognize private keys as .pem files and public keys as .crt files.
In C:\private you have your private and public key pairs which allow you to sign packets (mykey.pem and mykey.crt).
In c:\wapt\ssl you only have mykey.crt, this tells your agent that it accepts all Wapt packets from the mykey.pem key.
As for the files in c:\wapt\private, they are completely internal to Wapt; you don't need them.
For more information, see: https://www.wapt.fr/fr/doc/wapt-securit ... urn-states.
Regarding the certificate, which is potentially located in c:\wapt\wapt\ssl\server, see:
https://www.wapt.fr/fr/doc/wapt-securit ... apt-agents
Hello,
thank you for the clarification.
I'm facing another issue: package uploading.
When I go to "Tools," then "Generate Package Template," the "Create and Upload" button remains grayed out.
I have to go to "Create and Edit," then go to the PyScripter project explorer and type "-i build-upload."
I saw that I needed to set the prefix and enter the certificate in the WAPT console preferences, but that didn't change anything.
Thank you in advance.
thank you for the clarification.
I'm facing another issue: package uploading.
When I go to "Tools," then "Generate Package Template," the "Create and Upload" button remains grayed out.
I have to go to "Create and Edit," then go to the PyScripter project explorer and type "-i build-upload."
I saw that I needed to set the prefix and enter the certificate in the WAPT console preferences, but that didn't change anything.
Thank you in advance.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
That's normal if it's an executable file, since the package must be tested before upload (using an uninstall key, etc.)
https://www.youtube.com/watch?v=z_EN2CBCTcY
