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
The search returned 7 results
- March 27, 2025 - 10:31
- Forum: WAPT Server
- Subject: [SOLVED] No authorization token - Windows Agent
- Answers: 12
- Views : 44343
- March 10, 2025 - 3:45 PM
- Forum: WAPT Server
- Subject: [SOLVED] No authorization token - Windows Agent
- Answers: 12
- Views : 44343
Re: No authorization token - Windows Agent
Hello,
thank you for your reply.
I'm waiting for information from "official support" and will contact them.
For context, there is no reverse proxy or SSL interception.
In the /opt/wapt/conf/waptserver.ini file, use_ssl_client_auth is set to False.
I'll look into it...
thank you for your reply.
I'm waiting for information from "official support" and will contact them.
For context, there is no reverse proxy or SSL interception.
In the /opt/wapt/conf/waptserver.ini file, use_ssl_client_auth is set to False.
I'll look into it...
- March 10, 2025 - 09:20
- Forum: WAPT Server
- Subject: [SOLVED] No authorization token - Windows Agent
- Answers: 12
- Views : 44343
Re: No authorization token - Windows Agent
Hello,
Unless I'm mistaken, I haven't received any feedback on this issue.
We have purchased licenses and are unable to go live due to this problem. Could you please get back to me?
Best regards,
SMA
Unless I'm mistaken, I haven't received any feedback on this issue.
We have purchased licenses and are unable to go live due to this problem. Could you please get back to me?
Best regards,
SMA
- February 27, 2025 - 11:52
- Forum: WAPT Server
- Subject: [SOLVED] No authorization token - Windows Agent
- Answers: 12
- Views : 44343
Re: No authorization token - Windows Agent
Hello,
do you have any suggestions regarding this issue?
Thank you in advance,
Best regards,
SMA
do you have any suggestions regarding this issue?
Thank you in advance,
Best regards,
SMA
- February 20, 2025 - 4:55 PM
- Forum: WAPT Server
- Subject: [SOLVED] No authorization token - Windows Agent
- Answers: 12
- Views : 44343
Re: No authorization token - Windows Agent
Hello,
In the /var/log/waptserver.log file, the message mentioned in my first post appears:
Feb 20 16:44:26 SL346 waptserver[28606]: 2025-02-20 16:44:26,147 [waptws] WARNING SocketIO connection
refused for uuid rnd-1908c904-5d54-4cc1-86-09-46-2f-7a-5d-97-ac, sid ZkfqMJ9bS1IlfcR0ADkV ...
In the /var/log/waptserver.log file, the message mentioned in my first post appears:
Feb 20 16:44:26 SL346 waptserver[28606]: 2025-02-20 16:44:26,147 [waptws] WARNING SocketIO connection
refused for uuid rnd-1908c904-5d54-4cc1-86-09-46-2f-7a-5d-97-ac, sid ZkfqMJ9bS1IlfcR0ADkV ...
- February 19, 2025 - 10:50 PM
- Forum: WAPT Server
- Subject: [SOLVED] No authorization token - Windows Agent
- Answers: 12
- Views : 44343
Re: No authorization token - Windows Agent
Hello,
First of all, thank you for acknowledging the request and for your feedback.
Below you will find the content:
2025-02-19 22:41:10,040 [waptcore MainThread 5528] DEBUG Thread 5528 is connecting to wapt db
2025-02-19 22:41:10,041 [waptcore MainThread 5528] DEBUG DB Start ...
First of all, thank you for acknowledging the request and for your feedback.
Below you will find the content:
2025-02-19 22:41:10,040 [waptcore MainThread 5528] DEBUG Thread 5528 is connecting to wapt db
2025-02-19 22:41:10,041 [waptcore MainThread 5528] DEBUG DB Start ...
- February 17, 2025 - 11:47
- Forum: WAPT Server
- Subject: [SOLVED] No authorization token - Windows Agent
- Answers: 12
- Views : 44343
[SOLVED] No authorization token - Windows Agent
Hello,
I'm currently experiencing a "post-registration" issue with agents on the WAPT server.
Machine registration via Kerberos is working correctly, and the workstation appears in the console, but the status remains "Disconnected"
on the client side, as shown in the waptservice.log...
I'm currently experiencing a "post-registration" issue with agents on the WAPT server.
Machine registration via Kerberos is working correctly, and the workstation appears in the console, but the status remains "Disconnected"
on the client side, as shown in the waptservice.log...
