Ticket #99 (assigned enhancement)
Add JARs to manifest for compatibility with SSL Acceptors
| Reported by: | msanderse | Owned by: | gerco |
|---|---|---|---|
| Priority: | minor | Milestone: | Future |
| Component: | Sonic MQ | Version: | |
| Keywords: | SSL manifest.mf classpath | Cc: |
Description
If you add the following JARs to the manifest.mf MessageManager? can also send to & receive from SSL acceptors:
rsa_ssl.jar jsafeJCE.jar jsafe.jar certj.jar asn1.jar
Change History
comment:1 Changed 3 years ago by gerco
- Status changed from new to assigned
- Milestone changed from Sonic Message Manager 1.7 to Sonic Message Manager 1.6.2
comment:2 Changed 3 years ago by gerco
- Milestone changed from Sonic Message Manager 1.6.2 to Sonic Message Manager 1.7
I added the following JAR files to the class path:
- sonic_SSL.jar (to prevent NoClassDefFoundError on !ProgressSSLSocketFactory)
- rsa_ssl.jar
- asn1.jar
- certj.jar
- jsafe.jar
- jsafeJCE.jar
- sslj.jar (To prevent NoClassDefFoundError on !SSLException)
Now it complains about not being able to find a trusted CA certificate for the acceptor (SSL acceptor with default settings on the broker). To make SSL work, we need some way of configuring certificates for the web start application.
Besides that, we also need to solve the problem that the sonic client libraries do not abort the connection when an SSL failure occurs. It just retries seemingly infinitely without a change to alert the user to the failure (errors appear on stderr or stdout, but no Exceptions occur).
Postponed for now :(
comment:3 Changed 3 years ago by gerco
- Milestone changed from Sonic Message Manager 1.7 to Sonic Message Manager 2.0
Re-planned because impact is too great for minor release.
