Below is a list of versions that are available for the xmppweb plugin. To find other plugins, please review this listing of most recent releases of all plugins.

Plugins extend and enhance the functionality of Openfire. To install plugins, copy the .jar file into the plugins directory of your Openfire installation.

Xmppweb Plugin Readme

Overview

The Xmppweb plugin adds the web client to Openfire. XMPP Web is a third party web client implementation. It's project home page is https://github.com/nioc/xmpp-web

Installation

Copy xmppweb.jar into the plugins directory of your Openfire installation. The plugin will then be automatically deployed. To upgrade to a new version, copy the new xmppweb.jar file over the existing file.

Configuration

The plugin is configured via the Openfire Admin Console. After installation, a new Admin Console page is available. The page can be found on a main menu in the "Web Clients" tab. The name of the page is "Xmppweb".

Xmppweb depends on Web binding, and will not work if the Web binding service of Openfire is disabled. It can be enabled on the Server > Server Settings > Web Binding page.

Most XMPP Web configuration properties can be specified, by setting them as a Openfire system property, prepended with xmppweb.config. (eg: xmppweb.config.connectTimeout).

Using the Plugin

When properly configured, the XMPP Web client will be made available on the same ports as the web binding interface. The exact URLs for your instance of Openfire are displayed on the XMPP Web Configuration Admin Console page. By default, these URLs are:

• http://<your-server-name>:7070/xmppweb/ (unencrypted HTTP)
• https://<your-server-name>:7443/xmppweb/ (encrypted HTTPS)

After opening one of these addresses in a browser, the user is presented with a login form.