Default language.

Encrypting chat communications

Important

You cannot use Openfire Chat if your browser does not support Adobe Flash. We recommend using Smart IT Openfire Chat for agent-to-agent communication.


When the chat connections are not secure, the plain text messages that are exchanged between the browser and the chat server can be read by a person who is wire-tapping. This happens when the XMPPPortIsSecure property is set to false. For more security and for encrypting the communication, set the value of the XMPPPortIsSecure property to true.

For secure HTTP communication, set the value of the useHTTP and XMPPPortIsSecure properties to true and the value of the XMPPServerPort property as the HTTPS port number of the chat server (this value is usually 7443).

Note

When using HTTPS for chat, make sure that BMC Remedy Mid Tier is also running under HTTPS.

For secure non-HTTP communication, set the value of the useHTTP property to false and the value of the XMPPServerPort property to the TCP port of the chat server (this value is usually 5222 for the Openfire server).

Ports used by the Openfire chat server

By default, the Openfire server communication is done on ports 5222, 5223, 7070, or 7443. When you have a firewall, make sure that the communication is allowed for these ports for the Openfire server.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*