Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache License. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.
The Ignite Realtime Community is pleased to announce the release of version 3.10.3 of Openfire. This release continues our effort to produce a stable 3.10 release series of Openfire while we work toward the next major release of Openfire. The release is available now for download from our website.
Here are SHA-1 hashes for the download artifacts
Please note that we are no longer producing a Solaris build, due to perceived lack of interest and some strange with our Bamboo build agent. If you would like to help out with creating a Solaris build, please respond in the .
As a reminder, Openfire is developed by a group of volunteers and are always looking for more developers and testers to pitch in. Please stop by our XMPP chatroom email@example.com at any time and say if you are interested in helping out!
The Ignite Realtime community is very proud to release Openfire 3.10.0 for general availability from http://www.igniterealtime.org/downloads/
The amount of energy that has gone into this release is truly impressive, and it shows no signs of slowing down - as those of your looking at the 3.11 branch will have seen. Further 3.10.X releases will be bugfix releases; 3.11 will concentrate on a path to 4.0.0.
3.10.0 itself brings new core features to Openfire (such as Message Carbons, for example, by Christian Schudt) and vital improvements (to clustering and MUC, for example, by Tom Evans), as well as some hard bugfixing (by Guus der Kinderen) and important security improvements.
As ever, we welcome pull requests (to 3.10 or master as appropriate), and the entire development team is looking forward to you joining the conversation either in the forums or in the XMPP chatroom at firstname.lastname@example.org
UPDATE: Spark 2.6.3 version has issues with connecting to this version of Openfire. We suggest updating to just released 2.7.0 version of Spark.
UPDATE 2: Openfire 3.10.1 has been released recently, which is again compatible with Spark 2.6.3 when using TLS (thanks to this fix [OF-907] SSLv2 Hello is rejected; prevents some clients connecting - Jive Software Open Source )
The Ignite Realtime Community is pleased to announce a release candidate build of the upcoming 3.10.0 release. A lot of work has gone into this RC since the beta release a few months back and with your help testing, we are hoping to turn around a full 3.10.0 release very soon! Here are some of the highlights since the beta:
For those of you that track our progress on Github, we are starting a new approach for development going forward. An Openfire 3.10 branch has been created and the hope is that we will not have feature creep in this branch, but instead focus on stability and be able to make point releases when the situation warrants. In the past, Openfire's point releases (ie 3.9.0 to 3.9.1) was a mixture of bug fixes and new features. The new features will appear in other branches with an eye toward a future 3.11 or 4.0 release! We are always looking for more folks to help develop Openfire, so please send us those pull requests and stop by our XMPP MUC room email@example.com to say hi.
So please test this RC and report issues you find in the Openfire Support Forum. Do not report issues by commenting on this blog post please!
Here is a listing of download links and md5sums for this release. You can find these also on our beta download page.
The Ignite Realtime Community is pleased to announce that Openfire version 3.9.3 is available for download!
Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache license. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.
This release corrects the regressions found with the 3.9.2 release, which include:
A full changelog can be found here.
We'd invite interested developers to fork our github repository and contribute pull requests with your fixes. Ongoing discussions are happening in the community forums about the future of Openfire development. Please join in if you are interested!
Please report bugs with this release in the community forums. Please do not report bugs by commenting on this blog post!
Here are md5sum's for the released files:
The Igniterealtime community and Jitsi.org is proud to release the Jitsi Videobridge plugin for Openfire version 1.3.0 with Openfire 3.9.2. The new version has the latest code from the Jitsi project, fixes a number of issues and implements some requests made from the community
To run the ofmeet video conference application, point your browser at https://your_server:7443/jitsi/apps/ofmeet
To run the Candy web application with multi-user video, point your browser at https://your_server:7443/jitsi/apps/candy
To download the Spark plugin, point your browser at https://your_server:7443/jitsi/apps/spark/jitsivideobridge-plugin.jar
To run the jitmeet video conference application, point your browser at https://your_server:7443/jitsi/apps/jitmeet
You will need Google Chrome as your default browser to use the Spark plugin
Although jitmeet (Jitsi Meet) and ofmeet (Openfire Meetings) look similar, they are different underneath and are heading in different directions.
Jitsi Meet is for generic XMPP servers and aimed at public internet facing conferencing using services like prezi.org and etherpad.org while Openfire Meetings is for private in-house conferencing where all collaboration applications are integrated into Openfire. For example, Ofmeet uses a PDF viewer which supports in-house corporate powerpoint presentations, while Jitmeet uses prezi.org.