Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
First of all, great work with the Jabber plugin!
There are issues with certain Jabber servers that must require the SSLSocketFactory to connect to.
This feature is available in Pidgin as "Force old (port 5223) SSL".
It would be great to offer something similar in the Jabber plugin
I succeeded in this with a simple program using the Smack 3.1.0 API and just setting the SocketFactory to SSLSocketFactory.getDefault() as you see below:
ConnectionConfiguration config = new ConnectionConfiguration("<hostname>", 5223, "<servicename>");
config.setSocketFactory(SSLSocketFactory.getDefault());
XMPPConnection connection = new XMPPConnection(config);
connection.connect();
Attachments
Issue Links
- is related to
-
JENKINS-16383 add option for SSL connection instead of SASL
-
- Resolved
-
Activity
derekjchoi
added a comment - If I had control over the Jabber server, I'd certainly move away from SSL. I think this may be the case for many users. For large companies, things move at the rate of Molasses 
derekjchoi
added a comment - If I had control over the Jabber server, I'd certainly move away from SSL. I think this may be the case for many users. For large companies, things move at the rate of Molasses
derekjchoi
added a comment - patch derekjchoi
added a comment - continuation of patch, attached help-ssl.html 
kutzi
added a comment - Do you remember if you got a XMPPException when connectiong without you patch or did XMPPConnection#isConnected() simply returned false?
kutzi
added a comment - Do you remember if you got a XMPPException when connectiong without you patch or did XMPPConnection#isConnected() simply returned false? I can't wait to test this patch. Currently I'm not able to use Jabber notifications because our corporate IM jabber server works only with old SSL 5332 port. Pidgin works but hundson doens't.
There is no chance of upgrading the Jabber server because it is maintained by IT 
Code changed in hudson
User: : kutzi
Path:
trunk/hudson/plugins/jabber/src/main/java/hudson/plugins/jabber/im/transport/JabberIMConnection.java
http://jenkins-ci.org/commit/36176
Log:
JENKINS-6863 transparently fall back to legacy SSL if connect fails
kutzi
added a comment - It would be great if someone could try the attached development versions of the plugins.
kutzi
added a comment - It would be great if someone could try the attached development versions of the plugins. kutzi
added a comment - Note: if adapted the patch so that the bot falls back transparently to legacy SSL when the 1st connection attempt fails. So no new configuration option to force legacy SSL.
kutzi
added a comment - Note: if adapted the patch so that the bot falls back transparently to legacy SSL when the 1st connection attempt fails. So no new configuration option to force legacy SSL. kutzi
added a comment - Fixed in Jabber plugin 1.2 
mirabilos
added a comment - +1 from me (and thanks for re-adding in current plugin versions),
Port 5223 SSL is required because the firewall blocks Port 5222
connections to the jabberd to force the use of SSL here.
mirabilos
added a comment - +1 from me (and thanks for re-adding in current plugin versions),
Port 5223 SSL is required because the firewall blocks Port 5222
connections to the jabberd to force the use of SSL here. 
I wonder which Jabber server you are using, which still requires legacy SSL?
I mean, it's called 'legacy' with a reason: any halfway recent server shouldn't need it anymore.
Can't you upgrade your server to a newer version which can handle the standard SSL?
I've removed legacy SSL support in v1.7 of the plugin and I would really like to leave it this way - it's always good to throw away some old stuff, when it's not needed anymore.