[JIRA] (JENKINS-16383) add option for SSL connection instead of SASL

[trba...@adobe.com (JIRA)]

Trevor Baker commented on JENKINS-16383 add option for SSL connection instead of SASL I found the logging in tomcat's stderr file, which somehow is not making its way into the Jenkins log ui. It looks like a 401 is being returned. Jan 23, 2013 11:49:58 AM hudson.plugins.jabber.im.transport.JabberIMConnection createConnection INFO: Trying to connect to XMPP on im.mycorp.com:5223/im.mycorp.com with SASL Jan 23, 2013 11:50:58 AM hudson.plugins.jabber.im.transport.JabberIMConnection retryConnectionWithLegacySSL INFO: Retrying connection with legacy SSL Jan 23, 2013 11:51:00 AM hudson.plugins.jabber.im.transport.JabberIMConnection connect WARNING: not-authorized(401) at org.jivesoftware.smack.NonSASLAuthentication.authenticate(NonSASLAuthentication.java:109) at org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:212) at hudson.plugins.jabber.im.transport.JabberIMConnection.createConnection(JabberIMConnection.java:319) at hudson.plugins.jabber.im.transport.JabberIMConnection.connect(JabberIMConnection.java:162) at hudson.plugins.jabber.im.transport.JabberIMConnectionProvider.createConnection(JabberIMConnectionProvider.java:42) at hudson.plugins.im.IMConnectionProvider.create(IMConnectionProvider.java:65) at hudson.plugins.im.IMConnectionProvider.access$600(IMConnectionProvider.java:22) at hudson.plugins.im.IMConnectionProvider$ConnectorRunnable.run(IMConnectionProvider.java:183) at java.lang.Thread.run(Thread.java:722) Using the same credentials with Adium and Pidgin work using the "force old sytle ssl" option.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira