Tranquil IT Forum

Hello,
in my company, we have a certificate with the character *. I would like to use it in WAPT.
The integration with nginx doesn't pose any particular problem. However, when I try to retrieve the certificate from the WAPT console,
the file format is incorrect (unable to create file ..."C:\program Files(x86)\..\*.my_domain.fr.crt").
Windows doesn't support this character, which is normal.

Would it be possible to convert it to "star.my_domain.fr.crt" or some other workaround?

Thank you.

I forgot to mention:
tests performed with:
server: WAPT1.8.2 under CentOS 7.8;
consoles: Windows Server 2016

Could you be more specific about the phrase "However, when I try to retrieve the certificate from the WAPT console," (which button)? If it's a valid commercial certificate, it should be recognized without needing to pin it. If the console actually creates a file with an asterisk in it when you try to pin it, that's definitely a bug. But pinning is normally done with a specific server, not a wildcard.

This message appears when I go to the preferences of the Amin console, and I click on "retrieving the HTTP server certificate"

Hello,
I didn't understand if I need to give you more details or if you're already considering my question?

Hi Pierck,

if the certificate is a commercial certificate, it should be recognized with the python-certifi bundle. Pinning can indeed provide additional security. If it's an internal certificate authority, it's cleaner to create one certificate per server.

Importing the pinning through the interface doesn't work, but if you import your bundle manually, it should. The WAPT console's preferences menu will still indicate that it's not working, but it will run in the background.

If you have a WAPT commercial contract and this bug is important to you, you can contact Camille to have it prioritized. Alternatively, you can also submit a pull request on the WAPT GitHub repository.

Best regards,

Denis