Skip navigation
All Places > Ignite Realtime Blog
1 2 3 Previous Next

Ignite Realtime Blog

259 posts

The Ignite Realtime Community is proud to announce the 4.1.4 release of Openfire. This release signifies our continued effort to have a stable 4.1 release series while work progresses on the next major release.  A changelog exists denoting our 14 resolved issues and you can download the release builds from our website.  The following table contains a reference of release build files, their associated sha1sums and the number of times the previous release for that build type was downloaded.

OSsha1sumFilenameVersion 4.1.3 Downloads
Linux RPM (32bit JRE)8846cd55047d9871ef9357568e0c1a9f43c41652openfire-4.1.4-1.i686.rpm3,293
Linux RPM (No JRE)61a89afb66d74d523addbd238bf0c008ffada8aaopenfire-4.1.4-1.noarch.rpm2,249
Linux RPM (64bit JRE)8f370c7e9dfe530f7d05d93122ca72b9b563c92copenfire-4.1.4-1.x86_64.rpm12,142
Linux .deb83bf090c07daeacb59a97ddade1cd76c1dbb3030openfire_4.1.4_all.deb15,714
Mac OS37664eee2235748653ce070e873e5064a8e49bedopenfire_4_1_4.dmg4,095
Windows EXE1f417e66ec7ec729ff60cada797d112267370826openfire_4_1_4.exe43,598
Binary (tar.gz)6c8c262fbcc00c84bf86aab3787485e619757cc0openfire_4_1_4.tar.gz7,377
Binary (zip)25763a8273a5d7a66e322b3515c38dfa6c52dc6bopenfire_4_1_4.zip17,892
Source (tar.gz)680aad9967cef70ba609bb82854b9f991c8cd9c5openfire_src_4_1_4.tar.gz1,872
Source (zip)656ca8c2fe4679f340682e33e1042d6ae00f9ed3openfire_src_4_1_4.zip6,273

 

As a reminder, our development of Openfire happens on Github and we have an active MUC development chat hosted at  open_chat@conference.igniterealtime.org. We are always looking for more folks interested in helping out, so please consider pitching in!

 

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

Flow

Smack 4.2.0 released

Posted by Flow Champion Mar 20, 2017

Around two years ago, on 2015-03-29 to be precise, Smack 4.1.0 was tagged and released. A few days ago I've tagged and released Smack 4.2.0 to Maven Central. The 4.2.0 release marks a milestone for Smack, but before I got into the exciting new features, I'd like to thank the various contributors:

 

$ git shortlog -sn 4.1.0..4.2.0

   459  Florian Schmaus

     8  Fernando Ramirez

     3  Anno van Vliet

     3  Tibo-lg

     3  damencho

     3  ramabit

     2  Andrey Starodubtsev

     2  Vyacheslav Blinov

     2  stawny

     1  Andrey Prokopenko

     1  Craig

     1  Daniel Hintze

     1  Dave Cridland

     1  David Black

     1  Dmitry Deshevoy

     1  Grigory Fedorov

     1  Hugues Bruant

     1  Ishan Khanna

     1  TheHaf

     1  Tomas Nosek

     1  Tomáš Havlas

     1  UltimateZero

     1  Vaibhav

     1  meisterfuu

     1  rohanag12

     1  vfite

 

I can not remember when Smack had so many contributors. Thanks everyone and keep the contributions coming.

 

The notable changes to Smack 4.2 include support for DNSSEC (thanks to a previous MiniDNS GSOC project), JIDs as first class citizens by using JXMPP's JID API, and tons of other improvements, new features and bug fixes. You can read more in the Smack 4.2 Readme and Upgrade Guide and the Smack's JIRA release notes.

 

Last but not least, thanks to Bilal Siddiq, Smack now has a logo.

 

Ever wanted to contribute to open source? Are you interested in XMPP/DNS/DNSSEC? Google gives students the chance to work on open source projects and get paid for it as part of Google's Summer of Code 2017. The XSF acts as umbrella organization for projects like Smack and MiniDNS [4]. Feel free to contact me in the gsoc@muc.xmpp.org if you are interested in participating or if you want to discuss your own Smack/MiniDNS related project ideas.

Chrome version 57 makes a breaking change to webrtc that breaks Openfire Meetings. For details, read this.

You can apply a work-around by using the meetings settings admin web page to force a "negotiate" rtcpMuxPolicy as shown in the screen shot below.

 

ofmeet.jpg

 

Otherwise, upgrade to version 0.3.29 from github here.

 

The 0.4.x branch is now up-to-date with the latest Jitsi code including the mobile Jitsi-Meet applications for iPhone and Android. It can be previewed from here. It is still work in progress. If you test it with the mobile app, enter the full URL of your Jitsi-Meet application (https://<your-server>:7443/ofmeet/jitsi-meet/<room name>) and ensure your Openfire allows anonymous xmpp connections.

For many years now, Google is orchestrating its "Summer of Code" program. GSoC aims to bring student developers into the open source community, during the summer holidays.

 

As it did before, the XMPP Standards Foundation (XSF) will act as an umbrella organisation for this years edition of GSoC. The Ignite Realtime community is open to accept students under this umbrella.

 

If you're a student and interested in working on one of our projects as part of GSoC, you should get in contact! We've prepared a number of teaser tasks as well as project ideas, all of which are available in the XSF wiki.

I have added Kaiwa XMPP web client to the Chat API plugin. I hope to extend it with the audio/video conferencing stuff from Openfire Meetings later on.

kaiwa2.jpg

First time you use it (https://your_server:7443/apps), you will get a prompt to enter your Openfire username/password. It works best with the websocket plugin.

Daryl Herzmann

Openfire 4.1.3 Release

Posted by Daryl Herzmann Champion Feb 24, 2017

The Ignite Realtime Community is pleased to announce the 4.1.3 release of Openfire.  This release signifies our continued effort to have a stable 4.1 release series while work progresses on the next major release.  This release hopefully resolves the roster group issues noticed in Openfire since the 4.1.0 release.

 

You can find our release builds here and this is a listing of sha1sums and an accounting of previous version downloads.

OS
sha1sum
FilenameVersion 4.1.2 Downloads
Linux RPM (32bit JRE)

2b84acd3dbe6648ec4b08c81d912405d2ba78d5b

openfire-4.1.3-1.i686.rpm459
Linux RPM (No JRE)b18f1b51bf131b7aff90af92fd4c7dce79ca2d51openfire-4.1.3-1.noarch.rpm335
Linux RPM (64bit JRE)d9c52cd0029feb5e8b916410cea55d654f56b54b openfire-4.1.3-1.x86_64.rpm1413
Linux .debda7ea0c5bd48c519b4b4a10a5af9160d77dce30bopenfire_4.1.3_all.deb2440
Mac OSa76aa1612fa8066d76bab191f6fb7885b62c4195 openfire_4_1_3.dmg506
Windows EXE12110eaa952c2bb9f0142aa5ecd67bde399ce5beopenfire_4_1_3.exe5104
Binary (tar.gz)163c4f21bf34528fe3909e5be405d156911874feopenfire_4_1_3.tar.gz1066
Binary (zip)fde35bc78d875ceb83d9c39be7d2f1a71c9c640aopenfire_4_1_3.zip1147
Source (tar.gz)f270729ee6c7c530a7e927d728da7f136ff136f7openfire_src_4_1_3.tar.gz206
Source (zip)a04a712c0a9a73acc4c6f4b8b3fbd812528d65b2openfire_src_4_1_3.zip687

 

As a reminder, our development of Openfire happens on Github and we have an active MUC development chat hosted at  open_chat@conference.igniterealtime.org. We are always looking for more folks interested in helping out, so please consider pitching in!

 

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

Most of our projects have a long history. This certainly goes for Spark, which was created over ten years ago. Although many of you are actively using Spark today, it is beginning to show its age. This is something that we have been planning to address for a while now.

 

Spark was created around the same time that the Kyoto protocol went into effect, Pluto got demoted to the status of 'dwarf planet' and Italy won the FIFA world cup in Germany. Thereabouts.

 

Comment.jpgSince then, source code development tooling has improved a lot. Today, the Spark project is struggling to find active contributors. We believe that one of the reasons for this is that it's pretty hard for developers (especially those that are used to work with modern tooling) to get started with our project. We have been working on that. First, we moved all of our projects from our old Subversion repository to Github. We have noticed that this dramatically improved the accessibility of our code. Second, Smack 4 happened, bringing the backbone of Spark back up-to-date.

 

Now, we are addressing the structure of the project itself. We will restructure the project as a Apache Maven project. This will bring a good deal of predictable structure to the project, which has many benefits. One of these is that the project will integrate easily with various development tools.

 

Moving Spark from its existent Ant-based structure to a Maven structure is no small task. There is no one right way of doing this. We have given it a shot and have created a structure that we think is very workable. Before committing to this structure, we would very much invite others to have a look, and comment on what we've done. The reasoning behind this is simple: once we've committed to a particular structure, it will be disruptive to change it. If we want to apply improvements, we should do so now.

 

Please, review our new project structure, and let us know what you think. You can find the new structure in the SPARK-1791_Maven branch on Github.

 

Ask yourselves: does this structure help me? Is it easier to compile the source code? Can I integrate it with my IDE of choice without too much trouble? Can I create new plugins? Does the new structure introduce a problem that needs to be addressed before committing? Can it be improved? We welcome all feedback!

Dele Olajide

Openfire Chat API

Posted by Dele Olajide Champion Feb 18, 2017

I am trying to build a new web based client for Openfire to replace the outdated and abandoned Flash-based Sparkweb. The project is called Pade (A Yoruba word for Meeting) and my first step was to decide on my web client API.

 

Representational state transfer (REST) has now become the standard for abstracting request/response type web services into an API. When it is combined with Server Sent Events (otherwise known as Event Source), the result is a fresh new way of providing two-way real-time communication between web clients and a server using synchronous requests/responses (IQ) with REST and asynchronous evening (Message, Presence) with SSE. The really cool feature of SSE is the automatic re-connection by the web browser.

 

The Rest API plugin by Redor is brilliant . It allows you to administer Openfire via a RESTful API. Most of the common functions we do from the Openfire admin console web application can now be automated and integrated into server-side Java plugins or client-side web applications with ease. After spending hours inside the code and extending it for use at work to manage all the telephony entities we use with our Openlink XEP from the various commercial plugins we develop, it became clear that REST+SSE is the way forward for web-based real time messaging. Don't take my work for it. Read what the folks at erlang-solutions.com have to say.

 

As my first step towards implementing Pade, I have built a Chat API plugin by extending the REST API plugin with SSE and Jetty web authentication taken from the Openfire meetings plugin. The plugin now runs on the HTTP-BIND (7070/7443) port instead of the admin (9090/9091) port. It authenticates you as an Openfire user once and reuses the authentication for REST,  SSE and XMPP bosh/websockets. It supports everything you can do with the REST API plus Bookmarks and SIP Accounts as an admin user. It then enables you as a normal user to handle presence, chat, groupchat, contacts and users with just a handful of REST requests and SSE events.

 

Documentation can be found on GitHub Wiki pages

Daryl Herzmann

Openfire 4.1.2 Release

Posted by Daryl Herzmann Champion Feb 18, 2017

The Ignite Realtime Community is pleased to announce the availability of version 4.1.2 of Openfire. This release signifies our ongoing effort to produce a stable 4.1 series while effort is made on new features and functionality in Openfire 4.2.  You can find a release changelog denoting the 13 Jira issues resolved in this release.  If you had issues with inconsistent appearance of groups, do please test this release to see if those issues are now resolved. You can download the release from our website here and the sha1sum's for the available artifacts are as follows.

 

OSsha1sumFilenameVersion 4.1.1 Downloads [1]
Linux RPM (32bit JRE bundled)c2f12c3ec6ba2f64388279f106f2749272c9504copenfire-4.1.2-1.i686.rpm1290
Linux RPM (no JRE)226a7f1138fda7c456523bf80e6140e020fd5a74openfire-4.1.2-1.noarch.rpm965
Linux RPM (64bit JRE bundled)6892ec82e1435b6cbf23da1ba1efb9d94122d8a6openfire-4.1.2-1.x86_64.rpm3805
Linux .debc205eefe136fe0481e498668f258a0bc724a7080openfire_4.1.2_all.deb7311
Mac OS dmgb9570c78854c226714c23001997119e503e0aaabopenfire_4_1_2.dmg1207
Windows EXEdba34e78456f03bbd0de5a5cf94730c433d75c20openfire_4_1_2.exe19798
Binary (tar.tgz)cf4676f1e8c8a04999f6e9c97d859c8bbff35c4eopenfire_4_1_2.tar.gz2622
Binary (zip)0f4624f2c387c00373c717a52ed442741ceb0e93openfire_4_1_2.zip3058
Source (tar.gz)9b1efd5090ff37e4faca6d460b20ec40a4c40a53openfire_src_4_1_2.tar.gz408
Source (zip)b32c39ec84ad04acf46881b682919ef41fab3be4openfire_src_4_1_2.zip1371

 

[1] We recently migrated to storing our release artifacts on Github and thanks to their API, we can get metrics on how many times the artifact was downloaded.

 

As a reminder, our development of Openfire happens on Github and we have an active MUC development chat hosted at open_chat@conference.igniterealtime.org . We are always looking for more folks interested in helping out, so please consider pitching in!

 

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

Flow

Smack 4.2.0-rc3 released

Posted by Flow Champion Feb 11, 2017

I've just released Smack 4.2.0-rc3 to Maven Central. Smack 4.2.0 is scheduled to be released early Q2 2017, according to Smack's release life cycle. And right now, it looks like the train is right on time.

I am happy to announce that we are bringing back one of our older projects from the grave: the Asterisk-IM project! This project was started in 2005 by Jive Software, and can be used to integrate the Asterisk platform in Openfire. Due to a lack of manpower over the last few years, development stalled. No longer!

 

We have found the most excellent Marcelo Terres willing and able to take on the reigns as project lead for the project! Simultaneously a code contribution by Ron Arts brought back compatibility of the Asterisk-IM source code with both recent versions of Openfire, as well as Asterisk 13 - but more on that later, from Marcelo.

 

I am more than confident that the project is in good hands with Marcelo. Not only has Marcelo been a active manager of the primarily Brazilian-based Openfire community, he is heavily involved in the Asterisk project, going as far as to speaking on AstriCon 2016.

 

As of now, we restored references to the project in our Ignite Realtime community. There is some more work to be done: downloads still point to an older release, and we might be lacking a bit of project infrastructure (such as an issue tracker, dedicated community forum, etc), but I'll leave that to Marcelo to put in place as he sees fit.

 

Marcelo, thanks for doing this! I'm excited to have you on board (as far as you weren't already)!

wroot

Spark 2.8.3 Released

Posted by wroot Champion Jan 29, 2017

The Ignite Realtime community has just released Spark 2.8.3 and it can be downloaded from the Ignite Realtime: Downloads

 

This is a regular update. A few issues have been fixed. Bundled Java updated to the latest version. There is a new menu to view history of sent broadcasts and an option to login anonymously.

 

For a complete list of changes please check the Spark Changelog

 

We encourage developers to get involved with Spark project by providing feedback and patches in the forums or submitting pull requests to GitHub - igniterealtime/Spark: Cross-platform real-time collaboration client optimized for business and organizations.

 

Here is the list of contributors to this release (besides myself):

Michael  - fixed Advanced settings not being saved without opening that menu, always on top issue and changed behavior when Auto Login is hidden

Alexander198961 (Aleksander Kovtunenko) · GitHub  - added a feature to save broadcasts history and access it via a new menu option

Jerry  - added support for anonymous login

Guus der Kinderen  - fixed issue when joining a room with a duplicate nickname and improved build time by removing unneeded code style checks

Daryl Herzmann  - helped to clean up the code further (removing legacy CVS keywords)

speedy  - fixed issues with password not being deleted when it should and added log file rotating by size

Atalanttore (Ettore Atalan) · GitHub  - updated German translation

 

Here are sha1 checksums for the downloads:

b07a990109ec934e673e2bcb41a6be81a44e6131  spark_2_8_3.dmg

839226d42cea7778961d525a63c4a27c0f269250  spark_2_8_3.exe

526c46faafe3baf8c78bc69a024cfd752da57123  spark_2_8_3_online.exe

06542cac2db2611e3fcfcf7741fcfe242aa98d9f  spark_2_8_3.tar.gz

ea4bb09c4b55d102f69f974418a06a5c820b37c3  spark-2.8.3.rpm

9917c48e393e215c9aa1d14606b70dcb8531baf9  spark-2.8.3.src.rpm

6b6adbed00935cd01155355b796d4c504d49c18f  spark_2.8.3.deb

The Ignite Realtime community is proud to announce that nearly 2 years after the release of Smack 4.1, the first Release Candidate (RC) of Smack 4.2 has been uploaded to Maven Central. Smack 4.2 marks another milestone in the development of Smack. With the availability of the first RC, the API of Smack 4.2 was sealed. This means that now is the ideal time for Smack users to adopt their codebase to the new Smack 4.2 API, and eventually start using Smack 4.2 in the experimental/development branch of their codebase. Please consult the Smack 4.2 Readme and Upgrade Guide for more information.

 

I'd like to use this post also to draw your attention at a very important topic. The codebase of smack-core and -tcp has grown historically over the past 15 years. This is not an issue per se. Smack was well designed from the beginning, is now modular and not affected by bit rot. But especially on important class, namely XMPPTCPConnection, has come to age. It is based on threads, when it should use NIO. It uses triggers for state changes, when it should be designed as finite state machine. And some more. I know that a lot of people are affected by Smack creating at least 2 threads per connection (instead of using NIO). This all also contributed at some amount to the latest security vulnerability found in Smack (SMACK-739 / CVE 2016-10027).

 

The only solution to tackle this would be to re-implement the affected code from scratch. But needles to say that this also would require funding, as it is not a simple one weekend task. I hope to have the resource to do this at some point in the future. If you think you can help, or know someone who possibly would be interested support the funding, then please contact me.

Daryl Herzmann

Openfire 4.1.1 Release

Posted by Daryl Herzmann Champion Dec 31, 2016

The Ignite Realtime Community is pleased to announce the release of Openfire 4.1.1.  This release contains a few database related bugfixes that only impacted those who upgraded to 4.1.0 and particularly those using MySQL or SQL Server databases.

 

OSsha1sumFilename
Linux RPM (+32bit JRE)1a71272fbc29fb1239170f878ad803f3136082e1openfire-4.1.1-1.i686.rpm
Linux RPM (No JRE)d56d83eaeca9c1cfe750e9fdbf1b1b0ef9cda74fopenfire-4.1.1-1.noarch.rpm
Linux RPM (+64bit JRE)d17abe02887e991a442d2906e67dbf821ec82fdfopenfire-4.1.1-1.x86_64.rpm
Linux Debianab16f19cbf56fdf592c3cb367e867079c7bbf9b4openfire_4.1.1_all.deb
Mac DMGc5d09b44e4bba74e04b0029799f4b6e6f1b190fdopenfire_4_1_1.dmg
Windows EXE762bbb2d2aa38ecb00c9b50841a9055d52ebd9deopenfire_4_1_1.exe
Binary (tar.gz)36157c519b323007acd2067739e27fe242b58465openfire_4_1_1.tar.gz
Binary (zip)ae67a8763b0a4c7bf64b97becd22f07ee5233369openfire_4_1_1.zip
Source (tar.gz)01b060137c44e215acfcb30f77dae159cc4b5a06openfire_src_4_1_1.tar.gz
Source (zip)28cb1739d0c2bdc1aacfc8d7639a7a9ee38532d9openfire_src_4_1_1.zip

 

You can download it from here:

Ignite Realtime: Downloads

As a reminder, Openfire's source code and development can be found on Github and an active developer discussion occurs within our open_chat@conference.igniterealtime.org groupchat.  Please consider helping out with Openfire's development!

 

As always, please report issues in the Community Forums and thanks for your interest in Openfire.

Christmas has come early.

 

Our github repository - GitHub - igniterealtime/Openfire: A XMPP server licensed under the Open Source Apache License. - reached a thousand and one stars today, so we've celebrated by releasing Openfire 4.1.0, containing over 150 fixes and new features. I feel I should personally thank Daryl Herzmann and Guus der Kinderen in particular for the gargantuan effort they've both put into this release, but we're also very lucky to have a large number of developers within the community providing us with high-quality patches via Pull Requests. This is, once again, a huge collective effort.

 

Changlog: Openfire Changelog

 

 

Platform
sha1sumFilename
Mac

3e245dc7cd67707847bba605ec4942a81438066d

openfire_4_1_0.dmg
Windowsd590ebf8e3ca429b1d738833e14419c3dd514110openfire_4_1_0.exe
Binary (tar.gz)

074021df4cc60af0f18879421c3b9e11316dad91

openfire_4_1_0.tar.gz
Binary (zip)

2e933881c80d9ded13027679e6a0465f20d812eb

openfire_4_1_0.zip
Source (tar.gz)cf458223b8acf23c84219f343d5d14bebfe9a963openfire_src_4_1_0.tar.gz
Source (zip)a4a637354be17031be64f7cff9443584dde4022dopenfire_src_4_1_0.zip
RPM Installer (32-bit JRE)

8ed5af7cbd41b48c866dc756cd8d927c34b39400

openfire-4.1.0-1.i686.rpm
RPM Installer (64-bit JRE)

ec257c300732d00d323f44f02a6d97d4030068fa

openfire-4.1.0-1.x86-64.rpm
RPM Installer (No JRE)

88d8bb61f2437d0ad1612d6f6464bf5dacd2425d

openfire-4.1.0-1.noarch.rpm
DEB Installer9ea6b83a7aa9229be0358385e02985a9df04418eopenfire_4.1.0_all.deb

 

You can download it from here:

 

Ignite Realtime: Downloads

 

As a reminder, Openfire's source code and development can be found on Github and an active developer discussion occurs within our open_chat@conference.igniterealtime.org groupchat.  Please consider helping out with Openfire's development!  We can use help in about all areas of development, but especially:

  • experienced packaging developers to improve the install/upgrade experience on various platforms
  • developers interested in transitioning Openfire to Maven
  • testing of Bamboo generated builds

 

Thank you for your interest in Openfire!

Filter Blog

By date: By tag: