Below is a list of versions that are available for the inverse 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.

inVerse Plugin Readme

Overview

The inVerse plugin adds the web client to Openfire. inVerse is a third party web client implementation. It's project home page is https://github.com/jcbrand/inverse.js

Installation

Copy inverse.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 inverse.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 "inVerse".

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

Most Converse configuration properties can be specified, by setting them as a Openfire system property, prepended with inverse.config. (eg: inverse.config.ping_interval).

Using the Plugin

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

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

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