[SOLVED] No authorization token - Windows Agent

Questions about WAPT Server / Requests and help related to the WAPT server
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
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

March 10, 2025 - 3:55 PM

The default Wapt configuration is "use_ssl_client_auth=True".

You can try changing this value and then running postconf to see if it's better.

Version 2.6 is now quite stable.

The Windows Update issues with Windows 11 24h2 affected all versions.
sma
Messages: 7
Registration: February 17, 2025 - 11:17

March 27, 2025 - 10:31

Hello,

I can confirm that the problem was resolved by setting the WAPT configuration to "use_ssl_client_auth=True".
I thought this option was modifiable and allowed bypassing the client certificate verification.

Thank you for your feedback and help.

Best regards,

SMA
User avatar
dcardon
WAPT Expert
Messages: 1930
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

March 27, 2025 - 11:31

Hi Sébastien,

thanks for the feedback. :-)

"use_ssl_client_auth=False" should only be used in certain unusual cases (like a dodgy reverse proxy that doesn't support streaming mode), but in my opinion, it should be completely removed.

I'm marking this topic as resolved.

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked