EWaptPackageSignError: no matching private key found for signing using certificate SSL certificate cn="mycertificate".
I've tried with several different certificates I have, and none of them match
the indexes.
(Information in signature)
Private key error during import
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
Hello, after generating the .wapt file, I try to import it via the console and I consistently get the following error:
EWaptPackageSignError: no matching private key found for signing using certificate SSL certificate cn="mycertificate".
I've tried with several different certificates I have, and none of them match
the indexes.
(Information in signature)
EWaptPackageSignError: no matching private key found for signing using certificate SSL certificate cn="mycertificate".
I've tried with several different certificates I have, and none of them match
the indexes.
(Information in signature)
Server 1.7.4 - Win7 - Waiting for a Debian VM provided by TiT...
Win7 console - pyscripter 3.4.1
Win7 console - pyscripter 3.4.1
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
the private key must be right next to the selected certificate.
the private key must be right next to the selected certificate.
Yet that is indeed the case.
Here's what I have in C:\Program Files (x86)\wapt\private
and in SSL:
Here's what I have in C:\Program Files (x86)\wapt\private
- wapt certif.JPG (25.45 KB) Viewed 8554 times
- wapt certifssl.JPG (18.97 KB) Viewed 8554 times
Server 1.7.4 - Win7 - Waiting for a Debian VM provided by TiT...
Win7 console - pyscripter 3.4.1
Win7 console - pyscripter 3.4.1
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
You've confused
C:\Program Files (x86)\wapt\private with the agent certificates folder, which is for internal Wapt operation.
This folder should be ignored.
Your private key is most likely located in
C:\private.
C:\Program Files (x86)\wapt\private with the agent certificates folder, which is for internal Wapt operation.
This folder should be ignored.
Your private key is most likely located in
C:\private.
The previous captures were on the client machine with a console.
On the server machine I have this:
When generating a packet, do you need to use the server's certificate?
On the server machine I have this:
- wapt certifSrv.JPG (13.67 KB) Viewed 8542 times
Server 1.7.4 - Win7 - Waiting for a Debian VM provided by TiT...
Win7 console - pyscripter 3.4.1
Win7 console - pyscripter 3.4.1
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
There are a lot of files in c:\private.
You generated several keys???
I don't know which one is the correct key...
Only leave the correct keys in c:\private.
Your agent apparently only accepts keys ending in "ray".
Keep only ray-2019 and ray.pem in the folder.
Back up your data before deleting the other keys...
You generated several keys???
I don't know which one is the correct key...
Only leave the correct keys in c:\private.
Your agent apparently only accepts keys ending in "ray".
Keep only ray-2019 and ray.pem in the folder.
Back up your data before deleting the other keys...
wasted an hour struggling with certificates and keys.
I still don't understand what's needed on the console, even after rereading the documentation and regenerating the key/certificate.
Is there a way to work without it? Secure software is great, but if it doesn't work, it's useless.
I still don't understand what's needed on the console, even after rereading the documentation and regenerating the key/certificate.
Is there a way to work without it? Secure software is great, but if it doesn't work, it's useless.
Server 1.7.4 - Win7 - Waiting for a Debian VM provided by TiT...
Win7 console - pyscripter 3.4.1
Win7 console - pyscripter 3.4.1
Hello tice,
Certificate-based operation is at the heart of WAPT; it's what allows us to control access to the deployment on your network.
Without certificates, anyone could deploy anything on your network, which is precisely the situation we want to avoid with a tool like WAPT.
We understand that this operation may seem cumbersome, which is why we strive to maintain comprehensive documentation on this topic, available at https://www.wapt.fr/fr/doc/wapt-configu ... index.html.
Regarding your issue, the best advice I can give you is to reread the documentation, verifying at each step that everything is correct in your installation. Since we don't have access to your WAPT infrastructure, it's difficult for us to determine the best way to assist you.
I invite you to contact the sales department at +33 2 40 97 57 55 to discuss a potential support contract (our prices are very affordable) so we can best assist you.
Have a good day,
Camille
Certificate-based operation is at the heart of WAPT; it's what allows us to control access to the deployment on your network.
Without certificates, anyone could deploy anything on your network, which is precisely the situation we want to avoid with a tool like WAPT.
We understand that this operation may seem cumbersome, which is why we strive to maintain comprehensive documentation on this topic, available at https://www.wapt.fr/fr/doc/wapt-configu ... index.html.
Regarding your issue, the best advice I can give you is to reread the documentation, verifying at each step that everything is correct in your installation. Since we don't have access to your WAPT infrastructure, it's difficult for us to determine the best way to assist you.
I invite you to contact the sales department at +33 2 40 97 57 55 to discuss a potential support contract (our prices are very affordable) so we can best assist you.
Have a good day,
Camille
Camille FARGUES,
Account Manager
Account Manager
