This intends to prevent out-of-memory related Travis failures.

Using Statement instead of PreparedStatement

Ensure that LDAP configuration options are appropriately displayed

OF-1374: Fixed incorrect XML navigation in PEP auto-create

Admin console: apply JSTL to http-bind page.

Support UPN OID extraction directly in SANCertificateIdentityMapping

Allow components to subscribe to nodes

* OF-1370: inVerse plugin: hide registration tab.

When a user cannot register (if the domain is locked, and IBR is disabled), registration options should not be shown.

* OF-1371: Upgrade inVerse to 3.2.1

This commit replaces the converse.js 3.1.0 release with version 3.2.1. Additionally, the plugin now contains a copy of jquery (where previously, a link to a CDN was used).

OF-1369: Skip IBR when readonly user provider

There's no point in offering in-band registration when the user provider disallows any modifications.

* OF-1208: Disallow (by default) S2S for anonymous users.

Fixing NullPointerException caused by having a mix of valid Groups and NULLs inside the result of getGroupsFromKeys

Openfire 4.2.0 will have the functionality that's now in the websocket plugin. As a result,
this plugin should not be used in Openfire 4.2.0. To facilitate this, we've defined a new concept
of 'priorToServerVersion' in OF-1353.

This commit defines that the plugin should only be used in Openfire instances prior to version 4.2.0.

websocket plugin has been broken since Openfire 4.1.4. This PR implements the missing code and fixes the issue

    @Override
   public ConnectionConfiguration getConfiguration()
   {
       // TODO Here we run into an issue with the ConnectionConfiguration introduced in Openfire 4:
       //      it is not extensible in the sense that unforeseen connection types can be added.
       //      For now, null is returned, as this object is likely to be unused (its lifecycle is
       //      not managed by a ConnectionListener instance).
       return null;
   }

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

* OF-1354 add option to CC to disable start a chat

This is a complex problem.  During setup, fetching xmppSettings from the session may fail due to an invalid session state maintained between the client browser and the server.  This is likely caused by a previous HTTPS session to the same server hostname setting a `JSESSIONID` that subsequently can not be overwritten by the current HTTP openfire-setup session.

This introduces i18n string `setup.invalid_session`