Anyone out there in JSS land using Web Help Desk with a Casper 9 discovery connection? If so are you seeing errors after upgrading to JSS 9.61?
Looks like there is an issues as JSS 9.61 switched SSL 3.0 for TLS (from the release note - [D-007876] The default server.xml file now only supports Transport Layer Security (TLS) and disables support for Secure Sockets Layer (SSL) v3.0.). Web Help Desk now errors out for us with this:
Encountered error(s) during synchronization:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
So...anyone seeing this? I have had conversations with both JAMF and Solarwinds (Web Help Desk) about this and I'm trying to collect info to pass on to them.
We have our discovering connection set up, but have not done a sync since 9.61 upgrade. I would be happy to run a sync and see what happens. It sounds like the sync does not occur at all? My only hesitation would be if you have already experienced corrupt database info. So I am clear, all you have seen is a no-go on a sync not data loss or corruption?
No data corruption. It's just that the sync does not complete. I wouldn't have noticed it either only I had a note to go and remove our old Casper 8 discovery connection last week (after the 9.61 update) and I saw it then.
Let me know if you are able to confirm what I'm seeing, or not!
It's related to the poodle vulnerability and effects earlier versions of JSS if you manually fixed it using the JAMF KB here
This vulnerability is fixed in newer versions of JSS.
Backup the server.xml file first, but try to remove the line suggested in step 3 to see if that fixes it. IF it doesn't, put the server.xml file back
1) Open the server.xml file in a text editor.
2) The server.xml file is located in /path/to/JSS/Tomcat/conf/.
3) Add the following attribute to the Connector element for port="8443" after the sslProtocol="TLS" attribute:
4) Save and close the server.xml file.
5) Restart Tomcat.>>
Of course this is less than ideal, less secure. We are putting a solarwinds ticket in on it, you all should too. Other user posted in earlier thread his ticket number with them (714076) with them so hopefully if enough people complain they'll address. And maybe someday they'll support iOS syncing?