<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Non-SASL Authentication Plugin Readme</title>
<style type="text/css">
BODY {
font-size : 100%;
}
BODY {
font-family : tahoma, verdana, arial, helvetica, sans-serif;
font-size : 0.8em;
}
H2 {
font-size : 10pt;
font-weight : bold;
}
A:hover {
text-decoration : none;
}
H1 {
font-family : tahoma, arial, helvetica, sans-serif;
font-size : 1.4em;
font-weight: bold;
border-bottom : 1px #ccc solid;
padding-bottom : 2px;
}
</style>
</head>
<body>
<h1>
Non-SASL Authentication Plugin Readme
</h1>
<h2>Overview</h2>
<p>
The Non-SASL Authentication plugin provides an implementation for authentication with Jabber servers and
services using the jabber:iq:auth namespace.simple, as specified in
<a href="http://xmpp.org/extensions/xep-0078.html">XEP-0078: Non-SASL Authentication</a>.
</p>
<p>
Note Well: The protocol implemented by this plugin has been superseded in favor of SASL authentication as specified
by the XMPP standards in RFC 3920 / RFC 6120, and is now obsolete. This plugin should not be installed in Openfire,
unless there is a pressing need for backwards compatibility with regards to XEP-0078.
</p>
<p>
In versions of Openfire prior to (and excluding) 4.1.0 the functionality provided in this plugin was part of the
base functionality of Openfire itself. Years after SASL was introduced as the preferred method of authentication in
XMPP (and the corresponding formal obsoletion of non-SASL authentication in 2008), support for Non-SASL
Authentication was dropped from Openfire in version 4.1.0. For environments where backwards compatibility is
required, this plugin can be used to restore Non-SASL Authentication functionality in Openfire.
</p>
<h2>Installation</h2>
<p>
Copy nonSaslAuthentication.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 nonSaslAuthentication.jar file over the existing
file.
</p>
</body>
</html>