Ahh, ok. I understand the problem then, and it is a Messenger one. XMPP defines a new way of handling TLS/SSL connections that Jive Messenger doesn’‘t implement yet. We’'re planning on adding support soon.
I am running Jive on Red Hat 3AS. The connecting clients will most likely be either GAIM or Gush on Windows XP. SSL is a mandate to our messenger solution. I have yet to get SSL to work with either client. I have tried forcing old SSL. Nothing appears to provide even a temporary solution.
Do I need to create my own certs, aside from the 127.0.0.1 cert already present? Am I missing something here?
Please let me know what I can do to get this up and going as quickly as possible.
I tried connection with Gush and Psi using the old SSL and both clients were able to connect with the server. But I was not able to connect using Gaim. Don’'t know what validation is Gaim doing. Maybe Gaim is not accepting self-signed certificates? Try using Psi and/or Gush to check that the server side part is ok. Once you are ok with the server you have to check which certificates is Gaim accepting.