Open Realtime.

Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.

Open Realtime.

Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.
Latest Blog Entries
Dele Olajide

Introducing Project Pd- Openfire Meetings

Pd is the Yoruba word for "Meet" and is also the name of a new project here at Ignite. Pd (the "p" is pronounced explosively) is the renamed Openfire Meetings Chrome Extension.

To install, visit the Google Play web store

You will need at least the following four openfire plugins to use it.

  • ofmeet
  • offocus
  • bookmarks
  • websocket (not needed if using OF 4.2)

Pd will fetch the logged in user's contact roster as well as all the bookmarks configured for the user. To see, the contacts, conference rooms and web page urls, right click on the Openfire icon.

A normal left click on the Openfire icon causes Pd to open into a Jitsi Meet video-conference with the currently selected contact or multi-chat room.

If the meeting is with a contact, then the meeting url is sent to the contact as a standard chat message. When Pd receives such a message, it displays a notification to the user.

Accepting the invitation opens the Jitsi Meet video-conference window.

Tags: 6
daryl herzmann

Openfire 4.2.0 Beta Release

The Ignite Realtime Community is thrilled to announce the availability of a beta quality release of Openfire 4.2.0. Downloads of release artifacts can be found on our beta release website and a changelog denoting 60 some Jira issues resolved is available as well.

So what has changed with Openfire 4.2? A lot! Some highlights:

  • XEP-0237 Roster Versioning
  • Server to Server (s2s) is more robust
  • The websocket functionality, previously in a plugin, was merged into core
  • The Admin Console now has a Pub-Sub administration interface
  • You can now manually test a Server to Server connection on the Admin Console
  • XEP-0198 Client Resumption is now available
  • A lot of polish and new handy functionality was added to the Admin Console
  • Openfire plugin loading is much more robust

Here is a listing of sha1sum values for the release binaries

f6b69035c848c7555d2710b26efbb6a927e86175  openfire-4.2.0-0.2.beta.i686.rpm
4142b5baf024b603949b64f3896964ed4dcab196  openfire-4.2.0-0.2.beta.noarch.rpm
eb6e993e2ea185da235a9039b227a676d96210a0  openfire-4.2.0-0.2.beta.x86_64.rpm
ffcf842fd9a64741140bfdde560c952a34db08a9  openfire_4.2.0.beta_all.deb
5077b1283d91e23880148fc9891a18af02fb5c68  openfire_4_2_0_beta_bundledJRE.exe
c6108509b29fb8339f444e0b766d212818560465  openfire_4_2_0_beta_bundledJRE_x64.exe
8c68a07c1933754af2042bc5cd76e2545a2bcdd6  openfire_4_2_0_beta.dmg
551015e80cf4a001a6f97deda869cbdde8f7151f  openfire_4_2_0_beta.exe
aff23069cac31aad0ee902077fd8cd4f85ea3c1f  openfire_4_2_0_beta.tar.gz
b8255d7d7cd06a35f3bf12cc38d3473aa34669a5  openfire_4_2_0_beta_x64.exe
b380d386c2f3b4007dc9755648c579b984b52389  openfire_src_4_2_0_beta.tar.gz

Our current intention is for a quick turnaround of this beta into a full release, so please do test it and let us know of troubles you find by either visiting our webchat or creating posts in our Discourse Openfire Dev Forum.

A big thanks goes out to our current developers for doing a lot of work to make this beta release happen. These include @dwd, @guus, @gdt, and others now submitting pull requests to our Github Repository. A special thanks goes to folks at Surevine who have been actively supporting Openfire development.

For those interested in development, here are some current talking points of where development stands.

  • A large whitespace pull request was made against the master-branch, which is now the 4.2.0 beta. The intention of this was to not frustrate all of you that maintain forks of Openfire :), but to make future Openfire contributions easier. The code base should now follow the Editor Config guidelines and so your IDE should be able to focus better on actual code changes and not fixing whitespace issues.
  • At this point, there is not much appetite for an additional 4.1 branch release, but that could of course change. We'd like to get 4.2.0 out the door, then branch master into a 4.2 branch and then focus on moving forward with 4.3 development and stabilizing 4.2 branch with a 4.2.1 release.
  • master branch continues to support building with ant and maven, with Install4j artifacts built from the ant side. We like to consolidate on maven, but work needs to be done in this area. Please consider contributing if you have maven/install4j expertise!

And in closing, please consider helping out with development. The needs are many, but some particular areas of interest are:

  • improving Openfire's LDAP implementation
  • Bringing core functionality like Multi User Chat (MUC) up to current specifications
  • Vastly improving Openfire's automated testing

We are an easy going bunch and I personally love chipping in to help out. We all hang out within the groupchat each day, so stop by! If your organization relies on Openfire, please consider helping out!

Hopefully everybody enjoys the beta release and we can turn around a full release shortly, thanks for reading and your support of Ignite Realtime!

Tags: planetjabber 11
daryl herzmann

Openfire 4.1.6 Release

The Ignite Realtime Community is proud to announce the 4.1.6 release of Openfire. This release signifies our continuing effort to produce stable 4.1 series releases while work continues on the next major release. A changelog denoting 16 resolved issues is available and you can download the release builds from our website.

Important to know: Openfire now automatically installs the service. On the last step of the installer you will have an option whether to start it or not (it will also open the browser pointing to Admin Console, if you chose to start it). You shouldn't run the launcher, if the service is started. Documentation is updated accordingly. If you already have older service running, stop it before upgrading. You don't have to do this when upgrading from 4.1.5 and with later versions. It should stop the service automatically.

The following table denotes release artifact sha1sums and some github download statistics for the 4.1.5 release of that particular file.

OS sha1sum Filename Version 4.1.5 Downloads
Linux RPM (32bit JRE) f05e664e8c71c87e9d22f9e4d9ee49fc70ac2ade openfire-4.1.6-1.i686.rpm 2,473
Linux RPM (No JRE) 23936a3e9131d72febe18e52d8778f4f27e14a21 openfire-4.1.6-1.noarch.rpm 2,463
Linux RPM (64bit JRE) c52c74de7661f894395287a3119dd39d217f7726 openfire-4.1.6-1.x86_64.rpm 12,027
Linux .deb f37349708220c7c3e3fb577088b9d0b995494a9f openfire_4.1.6_all.deb 18,206
Mac OS b0315762aab005bd4d9b6cf28fe86b897f35a236 openfire_4_1_6.dmg 4,095
Windows EXE (32bit, No JRE) 228ab4fb6a95679a98995f6751d7bfb6831d48e3 openfire_4_1_6.exe 49,948
Windows EXE (32bit JRE) 09ed1261cd485414ab4bdb080324ea8f2484b784 openfire_4_1_6_bundledJRE.exe n/a
Windows EXE (64bit, No JRE) 726e3b4a70e04532540b6ffdf3702d03f17e34c1 openfire_4_1_6_x64.exe n/a
Windows EXE (64bit JRE) 00bd41e6df267fd87621bd048ed033065103bc65 openfire_4_1_6_bundledJRE_x64.exe n/a
Binary (tar.gz) 8af96d080b92a6575cd07dbbcd07a63371d577fe openfire_4_1_6.tar.gz 6,786
Binary (zip) b46e998302c9860b1150cf0b20e0525f57dcb3b2 11,241
Source (tar.gz) 032b3bfdbaad71cb61cb5ed921b17f3a4e9694c6 openfire_src_4_1_6.tar.gz 1,399
Source (zip) 4d9fb6e997c220664a9b5cdc8a5764cf62a46c43 5,731

As a reminder, our development of Openfire happens on Github and we have an active MUC development chat hosted at We are always looking for more folks to pitch in with testing, fixing bugs, and development of new features. Please consider helping out!

As always, please report any issues in the Community Forums and thanks for using Openfire!

Tags: release, planetjabber, openfire 2
daryl herzmann

Migration of Community Forums to Discourse

For over a decade, the Jive Software collaborative software has provided our community with a feature rich home for forums, documents, blog posts, and other things. Due to decreased involvement by Jive in Ignite Realtime, sale of Jive Software to Aurea, and other issues "clouding" the future of our Jive cloud instance of this forum, it is time to migrate content to a new platform.

The new platform chosen is the open-source Discourse and you can find our instance here:

You can find some technical details on the work being done within our Jira instance: INFRA-12

Migration Timeline

The intention is to make this current forum instance go into a read-only state very soon (next day or so). This will allow for some time to double check the fidelity of the content migration as more users test things out. Hopefully there are no show-stopping bugs with the Discourse instance that would cause us to revert back

Your usernames may have changed

Account details were migrated to the Discourse instance, but there was not a one-to-one conversion of usernames due to some issues I won't expound upon here. Your email address did directly translate, so when you first attempt to log into Discourse, you will need to reset your password by providing a valid email address used by the current forum instance. We also plan to support Google Authenticator usage, so you can simply use your google account to log in. If you have any doubts that the current account information is correct with regards to your email address, please feel free to directly email me or stop by our web-based group-chat.

Once you have initially logged in, you should be able to update your account settings and change your username to whatever you wish to use for future logins.

What will happen to community website links?

The plan is to setup a transparent HTTP forwarding of most legacy community website URIs into the proper location within Discourse. So our migration should not break the web

What about RSS feeds, blog feeds, planetjabber, etc?

Indeed, there are some issues to be worked out yet with exactly how we will handle blogs, etc within Discourse. If you are a Discourse expert and want to help out, certainly let us know! There will be a period of whack-a-mole as we workout how this update impacts users and our software, for example the feed of content found on the Openfire Admin Console.

Wait, I don't like how feature X is setup within Discourse?

Please let us know your thoughts, this is certainly the time to make changes. Something may be currently setup in a matter that is just the default or something that just hasn't been looked into yet. I certainly do not consider myself an expert with Discourse, with this being my first instance setup!

I would like to thank @Alameyo, @wroot, @Flow, @benjamin and others for their help with getting Discourse up and running. And of course, a big thanks to Surevine for their current sponsorship of Ignite Realtime's Amazon Web Services presence.

In Closing

I am very thankful to Jive Software for their more than generous support of Ignite Realtime over the years. While the amount of source code written by Jive over the past few years has stopped for Ignite projects, their financial support of Ignite Realtime's servers and internet hosting remained steadfast. Speaking for @Matt Tucker here, I believe his vision was for Ignite Realtime to mature and become more self sustaining. Recently, a major step toward that goal was taken with the establishment of the Ignite Realtime Foundation and our migration to Amazon Web Services.

Thank you for reading this and your patience as issues are worked out with this migration.

Tags: 1

About the Ignite Realtime Blogs category

(Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters. Until you edit this description or create topics, this category won't appear on the categories page.)

Use the following paragraphs for a longer description, or to establish category guidelines or rules:

  • Why should people use this category? What is it for?

  • How exactly is this different than the other categories we already have?

  • What should topics in this category generally contain?

  • Do we need this category? Can we merge with another category, or subcategory?

Tags: 0