- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: SmartTask HTTPS POST requirement
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SmartTask HTTPS POST requirement
Hi,
I'm trying to add HTTPS POST method to SmartTask, but I got error message after getting fingerprint. This HTTPS server using self-signed certificate. What is the requirement of HTTPS POST?
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you specify the fingerprint of the self-signed certificate?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, Create a New SmartTask - Choose to Send Web request - Click Get Fingerprint - Popup Warning dialog(attached) - Click Continue - Got error message(attached).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
have the same question. The POST goes to an internal web app with an internal certificate from an internal CA. I can get the fingerprint without error.
But the Task itself complains that the SSL verification is not possible. Where can I import our root CA for this specific verification?
Regards,
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please open a service request for that
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Opened a case, but found the issue meanwhile myself.
Our web service did not support TLSv1, after changed that the verification worked.
Regards,
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The tool ssldump helped me to find the issue with the TLS version. If the web service is on a Linux box, it could help.
