mirror of
https://github.com/processone/ejabberd.git
synced 2024-11-26 16:26:24 +01:00
4035 lines
174 KiB
HTML
4035 lines
174 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
|
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
|
<HTML>
|
|
|
|
<HEAD>
|
|
|
|
<TITLE>Ejabberd 1.1.2 Installation and Operation Guide</TITLE>
|
|
|
|
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
|
<META name="GENERATOR" content="hevea 1.08">
|
|
<STYLE type="text/css">
|
|
.toc{list-style:none;}
|
|
.title{margin:auto;text-align:center}
|
|
.center{text-align:center;margin-left:auto;margin-right:auto;}
|
|
.flushleft{text-align:left;margin-left:0ex;margin-right:auto;}
|
|
.flushright{text-align:right;margin-left:auto;margin-right:0ex;}
|
|
DIV TABLE{margin-left:inherit;margin-right:inherit;}
|
|
PRE{text-align:left;margin-left:0ex;margin-right:auto;}
|
|
BLOCKQUOTE{margin-left:4ex;margin-right:4ex;text-align:left;}
|
|
.part{margin:auto;text-align:center}
|
|
SPAN{width:20%; float:right; text-align:left; margin-left:auto;}
|
|
</STYLE>
|
|
</HEAD>
|
|
|
|
<BODY >
|
|
<!--HEVEA command line is: hevea -fix -noiso -pedantic guide.tex -->
|
|
<!--HTMLHEAD-->
|
|
<!--ENDHTML-->
|
|
<!--PREFIX <ARG ></ARG>-->
|
|
<!--CUT DEF section 1 -->
|
|
|
|
<BR>
|
|
<BR>
|
|
<A NAME="titlepage"></A>
|
|
|
|
<TABLE CLASS="title">
|
|
<TR><TD>
|
|
<H1 CLASS="titlemain">Ejabberd 1.1.2 Installation and Operation Guide</H1>
|
|
<H3 CLASS="titlerest">Alexey Shchepin<BR>
|
|
<A HREF="mailto:alexey@sevcom.net"><TT>mailto:alexey@sevcom.net</TT></A><BR>
|
|
<A HREF="xmpp:aleksey@jabber.ru"><TT>xmpp:aleksey@jabber.ru</TT></A></H3></TD>
|
|
</TR></TABLE><BR>
|
|
<BR>
|
|
<DIV CLASS="center">
|
|
|
|
<IMG SRC="logo.png" ALT="logo.png">
|
|
|
|
|
|
<BR>
|
|
<BR>
|
|
|
|
</DIV>
|
|
<BLOCKQUOTE CLASS="quotation"><I>I can thoroughly recommend ejabberd for ease of setup —
|
|
Kevin Smith, Current maintainer of the Psi project</I></BLOCKQUOTE>
|
|
<!--TOC section Contents-->
|
|
|
|
<H2 CLASS="section">Contents</H2><!--SEC END -->
|
|
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc1">1 Introduction</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc2">1.1 Key Features</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc3">1.2 Additional Features</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc4">2 Installation from Source</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc5">2.1 Installation Requirements</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc6">2.1.1 `Unix-like' operating systems</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc7">2.1.2 Windows</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc8">2.2 Obtaining <TT>ejabberd</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc9">2.3 Compilation</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc10">2.3.1 `Unix-like' operating systems</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc11">2.3.2 Windows</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc12">2.4 Starting</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc13">3 Basic Configuration</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc14">3.1 Host Names</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc15">3.2 Virtual Hosting</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc16">3.3 Listened Sockets</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc17">3.4 Authentication</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc18">3.4.1 Internal</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc19">3.4.2 SASL Anonymous and Anonymous Login</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc20">3.5 Access Rules</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc21">3.6 Shapers</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc22">3.7 Limiting Opened Sessions</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc23">3.8 Default Language</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc24">4 Database Configuration</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc25">4.1 MySQL</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc26">4.1.1 Driver Compilation</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc27">4.1.2 Authentication</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc28">4.1.3 Storage</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc29">4.2 Microsoft SQL Server</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc30">4.2.1 Driver Compilation</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc31">4.2.2 Authentication</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc32">4.2.3 Storage</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc33">4.3 PostgreSQL</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc34">4.3.1 Driver Compilation</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc35">4.3.2 Authentication</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc36">4.3.3 Storage</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc37">4.4 ODBC Compatible</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc38">4.4.1 Compilation</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc39">4.4.2 Authentication</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc40">4.4.3 Storage</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc41">4.5 LDAP</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc42">4.5.1 Connection</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc43">4.5.2 Authentication</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc44">4.5.3 Examples</A>
|
|
</UL>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc45">5 Modules Configuration</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc46">5.1 Overview</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc47">5.2 Common Options</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc48">5.2.1 <TT>iqdisc</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc49">5.2.2 <TT>hosts</TT></A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc50">5.3 <TT>mod_announce</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc51">5.4 <TT>mod_disco</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc52">5.5 <TT>mod_echo</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc53">5.6 <TT>mod_irc</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc54">5.7 <TT>mod_last</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc55">5.8 <TT>mod_muc</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc56">5.9 <TT>mod_muc_log</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc57">5.10 <TT>mod_offline</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc58">5.11 <TT>mod_privacy</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc59">5.12 <TT>mod_private</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc60">5.13 <TT>mod_pubsub</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc61">5.14 <TT>mod_register</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc62">5.15 <TT>mod_roster</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc63">5.16 <TT>mod_service_log</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc64">5.17 <TT>mod_shared_roster</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc65">5.18 <TT>mod_stats</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc66">5.19 <TT>mod_time</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc67">5.20 <TT>mod_vcard</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc68">5.21 <TT>mod_vcard_ldap</TT></A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc69">5.22 <TT>mod_version</TT></A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc70">6 Creating an Initial Administrator</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc71">7 Online Configuration and Monitoring</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc72">7.1 Web Interface</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc73">7.2 <TT>ejabberdctl</TT></A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc74">8 Firewall Settings</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc75">9 SRV Records</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc76">10 Clustering</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc77">10.1 How it Works</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc78">10.1.1 Router</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc79">10.1.2 Local Router</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc80">10.1.3 Session Manager</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc81">10.1.4 s2s Manager</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc82">10.2 Clustering Setup</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc83">A Internationalization and Localization</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc84">B Release Notes</A>
|
|
<UL CLASS="toc"><LI CLASS="li-toc">
|
|
<A HREF="#htoc85">B.1 ejabberd 0.9</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc86">B.2 ejabberd 0.9.1</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc87">B.3 ejabberd 0.9.8</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc88">B.4 ejabberd 1.0.0</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc89">B.5 ejabberd 1.1.0</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc90">B.6 ejabberd 1.1.1</A>
|
|
</UL>
|
|
<LI CLASS="li-toc"><A HREF="#htoc91">C Acknowledgements</A>
|
|
<LI CLASS="li-toc"><A HREF="#htoc92">D Copyright Information</A>
|
|
</UL>
|
|
|
|
<!--TOC section Introduction-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc1">1</A> <A NAME="intro">Introduction</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:intro"></A>
|
|
|
|
<TT>ejabberd</TT> is a free and open source instant messaging server written in <A HREF="http://www.erlang.org/">Erlang</A>.<BR>
|
|
<BR>
|
|
<TT>ejabberd</TT> is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.<BR>
|
|
<BR>
|
|
<TT>ejabberd</TT> is designed to be a rock-solid and feature rich XMPP server.<BR>
|
|
<BR>
|
|
<TT>ejabberd</TT> is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.<BR>
|
|
<BR>
|
|
<!--TOC subsection Key Features-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc2">1.1</A> <A NAME="keyfeatures">Key Features</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:keyfeatures"></A>
|
|
|
|
<TT>ejabberd</TT> is:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Cross-platform: <TT>ejabberd</TT> runs under Microsoft Windows and Unix derived systems such as Linux, FreeBSD and NetBSD.<BR>
|
|
<BR>
|
|
<LI CLASS="li-itemize">Distributed: You can run <TT>ejabberd</TT> on a cluster of machines and all of them will serve the same Jabber domain(s). When you need more capacity you can simply add a new cheap node to your cluster. Accordingly, you do not need to buy an expensive high-end machine to support tens of thousands concurrent users.<BR>
|
|
<BR>
|
|
<LI CLASS="li-itemize">Fault-tolerant: You can deploy an <TT>ejabberd</TT> cluster so that all the information required for a properly working service will be replicated permanently on all nodes. This means that if one of the nodes crashes, the others will continue working without disruption. In addition, nodes also can be added or replaced `on the fly'.<BR>
|
|
<BR>
|
|
<LI CLASS="li-itemize">Administrator Friendly: <TT>ejabberd</TT> is built on top of the Open Source Erlang. As a result you do not need to install an external database, an external web server, amongst others because everything is already included, and ready to run out of the box. Other administrator benefits include:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Comprehensive documentation.
|
|
<LI CLASS="li-itemize">Straightforward installers for Linux, Mac OS X, and Windows.<SPAN STYLE="font-variant:small-caps">improved</SPAN>
|
|
<LI CLASS="li-itemize">Web interface for administration tasks.
|
|
<LI CLASS="li-itemize">Shared Roster Groups.
|
|
<LI CLASS="li-itemize">Command line administration tool.<SPAN STYLE="font-variant:small-caps">improved</SPAN>
|
|
<LI CLASS="li-itemize">Can integrate with existing authentication mechanisms.
|
|
<LI CLASS="li-itemize">Capability to send announce messages.
|
|
</UL><BR>
|
|
<BR>
|
|
<LI CLASS="li-itemize">Internationalized: <TT>ejabberd</TT> leads in internationalization. Hence it is very well suited in a globalized world. Related features are:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Translated in 12 languages.<SPAN STYLE="font-variant:small-caps">improved</SPAN>
|
|
<LI CLASS="li-itemize">Support for <A HREF="http://www.ietf.org/rfc/rfc3490.txt">IDNA</A>.
|
|
</UL><BR>
|
|
<BR>
|
|
<LI CLASS="li-itemize">Open Standards: <TT>ejabberd</TT> is the first Open Source Jabber server claiming to fully comply to the XMPP standard.
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Fully XMPP compliant.
|
|
<LI CLASS="li-itemize">XML-based protocol.
|
|
<LI CLASS="li-itemize"><A HREF="http://ejabberd.jabber.ru/protocols">Many JEPs supported</A>.
|
|
</UL></UL>
|
|
<!--TOC subsection Additional Features-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc3">1.2</A> <A NAME="addfeatures">Additional Features</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:addfeatures"></A>
|
|
|
|
Moreover, <TT>ejabberd</TT> comes with a wide range of other state-of-the-art features:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Modular
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Load only the modules you want.
|
|
<LI CLASS="li-itemize">Extend <TT>ejabberd</TT> with your own custom modules.
|
|
</UL>
|
|
<LI CLASS="li-itemize">Security
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
SASL and STARTTLS for c2s and s2s connections.
|
|
<LI CLASS="li-itemize">STARTTLS and Dialback s2s connections.
|
|
<LI CLASS="li-itemize">Web interface accessible via HTTPS secure access.
|
|
</UL>
|
|
<LI CLASS="li-itemize">Databases
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Native MySQL support.
|
|
<LI CLASS="li-itemize">Native PostgreSQL support.
|
|
<LI CLASS="li-itemize">Mnesia.
|
|
<LI CLASS="li-itemize">ODBC data storage support.
|
|
<LI CLASS="li-itemize">Microsoft SQL Server support.<SPAN STYLE="font-variant:small-caps">new</SPAN>
|
|
</UL>
|
|
<LI CLASS="li-itemize">Authentication
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
LDAP and ODBC.<SPAN STYLE="font-variant:small-caps">improved</SPAN>
|
|
<LI CLASS="li-itemize">External Authentication script.
|
|
<LI CLASS="li-itemize">Internal Authentication.
|
|
</UL>
|
|
<LI CLASS="li-itemize">Others
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Compressing XML streams with Stream Compression (<A HREF="http://www.jabber.org/jeps/jep-0138.html">JEP-0138</A>).
|
|
<LI CLASS="li-itemize">Interface with networks such as AIM, ICQ and MSN.
|
|
<LI CLASS="li-itemize">Statistics via Statistics Gathering (<A HREF="http://www.jabber.org/jeps/jep-0039.html">JEP-0039</A>).
|
|
<LI CLASS="li-itemize">IPv6 support both for c2s and s2s connections.
|
|
<LI CLASS="li-itemize"><A HREF="http://www.jabber.org/jeps/jep-0045.html">Multi-User Chat</A> module with logging.<SPAN STYLE="font-variant:small-caps">improved</SPAN>
|
|
<LI CLASS="li-itemize">Users Directory based on users vCards.
|
|
<LI CLASS="li-itemize"><A HREF="http://www.jabber.org/jeps/jep-0060.html">Publish-Subscribe</A> component.
|
|
<LI CLASS="li-itemize">Support for virtual hosting.
|
|
<LI CLASS="li-itemize"><A HREF="http://www.jabber.org/jeps/jep-0025.html">HTTP Polling</A> service.
|
|
<LI CLASS="li-itemize">IRC transport.
|
|
</UL>
|
|
</UL>
|
|
<!--TOC section Installation from Source-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc4">2</A> <A NAME="installsource">Installation from Source</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:installsource"></A>
|
|
|
|
<!--TOC subsection Installation Requirements-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc5">2.1</A> <A NAME="installreq">Installation Requirements</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:installreq"></A>
|
|
|
|
<!--TOC subsubsection `Unix-like' operating systems-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc6">2.1.1</A> <A NAME="installrequnix">`Unix-like' operating systems</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:installrequnix"></A>
|
|
To compile <TT>ejabberd</TT> on a `Unix-like' operating system, you need:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
GNU Make
|
|
<LI CLASS="li-itemize">GCC
|
|
<LI CLASS="li-itemize">libexpat 1.95 or higher
|
|
<LI CLASS="li-itemize">Erlang/OTP R9C-2 or higher
|
|
<LI CLASS="li-itemize">OpenSSL 0.9.6 or higher (optional)
|
|
<LI CLASS="li-itemize">Zlib 1.2.3 or higher (optional)
|
|
<LI CLASS="li-itemize">GNU Iconv 1.8 or higher (optional, not needed on systems with GNU libc)
|
|
</UL>
|
|
<!--TOC subsubsection Windows-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc7">2.1.2</A> <A NAME="installreqwin">Windows</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:installreqwin"></A>
|
|
To compile <TT>ejabberd</TT> on a Windows flavour, you need:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
MS Visual C++ 6.0 Compiler
|
|
<LI CLASS="li-itemize"><A HREF="http://erlang.org/download.html">Erlang/OTP R9C-2 or higher</A>
|
|
<LI CLASS="li-itemize"><A HREF="http://sourceforge.net/project/showfiles.php?group_id=10127&package_id=11277">Expat 1.95.7 or higher</A>
|
|
<LI CLASS="li-itemize"><A HREF="http://www.gnu.org/software/libiconv/">GNU Iconv 1.9.1</A>
|
|
(optional)
|
|
<LI CLASS="li-itemize"><A HREF="http://www.slproweb.com/products/Win32OpenSSL.html">Shining Light OpenSSL</A>
|
|
(to enable SSL connections)
|
|
<LI CLASS="li-itemize"><A HREF="http://www.zlib.net/">Zlib 1.2.3 or higher</A>
|
|
</UL>
|
|
<!--TOC subsection Obtaining <TT>ejabberd</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc8">2.2</A> <A NAME="obtaining">Obtaining <TT>ejabberd</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:obtaining"></A>
|
|
|
|
Released versions of <TT>ejabberd</TT> can be obtained from <BR>
|
|
<A HREF="http://www.process-one.net/en/projects/ejabberd/download.html"><TT>http://www.process-one.net/en/projects/ejabberd/download.html</TT></A>.<BR>
|
|
<BR>
|
|
|
|
The latest development version can be retrieved from the Subversion repository.
|
|
<PRE CLASS="verbatim">
|
|
svn co http://svn.process-one.net/ejabberd/trunk ejabberd
|
|
</PRE>
|
|
<!--TOC subsection Compilation-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc9">2.3</A> <A NAME="compile">Compilation</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:compile"></A>
|
|
|
|
<!--TOC subsubsection `Unix-like' operating systems-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc10">2.3.1</A> <A NAME="compileunix">`Unix-like' operating systems</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:compileunix"></A>
|
|
Compile <TT>ejabberd</TT> on a `Unix-like' operating system by executing:
|
|
<PRE CLASS="verbatim">
|
|
./configure
|
|
make
|
|
su
|
|
make install
|
|
</PRE>
|
|
These commands will:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
install <TT>ejabberd</TT> into the directory <CODE>/var/lib/ejabberd</CODE>,
|
|
<LI CLASS="li-itemize">install the configuration file into <CODE>/etc/ejabberd</CODE>,
|
|
<LI CLASS="li-itemize">create a directory called <CODE>/var/log/ejabberd</CODE> to store log files.
|
|
</UL>
|
|
Note: if you want to use an external database, you need to execute the configure
|
|
script with the option(s) <TT>–enable-odbc</TT> or <TT>–enable-odbc
|
|
–enable-mssql</TT>. See section <A HREF="#sec:database">4</A> for more information.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Windows-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc11">2.3.2</A> <A NAME="compilewin">Windows</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:compilewin"></A>
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Install Erlang emulator (for example, into <CODE>C:\Program Files\erl5.3</CODE>).
|
|
<LI CLASS="li-itemize">Install Expat library into <CODE>C:\Program Files\Expat-1.95.7</CODE>
|
|
directory.<BR>
|
|
<BR>
|
|
Copy file <CODE>C:\Program Files\Expat-1.95.7\Libs\libexpat.dll</CODE>
|
|
to your Windows system directory (for example, <CODE>C:\WINNT</CODE> or
|
|
<CODE>C:\WINNT\System32</CODE>)
|
|
<LI CLASS="li-itemize">Build and install the Iconv library into the directory
|
|
<CODE>C:\Program Files\iconv-1.9.1</CODE>.<BR>
|
|
<BR>
|
|
Copy file <CODE>C:\Program Files\iconv-1.9.1\bin\iconv.dll</CODE> to your
|
|
Windows system directory (more installation instructions can be found in the
|
|
file README.woe32 in the iconv distribution).<BR>
|
|
<BR>
|
|
Note: instead of copying libexpat.dll and iconv.dll to the Windows
|
|
directory, you can add the directories
|
|
<CODE>C:\Program Files\Expat-1.95.7\Libs</CODE> and
|
|
<CODE>C:\Program Files\iconv-1.9.1\bin</CODE> to the <CODE>PATH</CODE> environment
|
|
variable.
|
|
<LI CLASS="li-itemize">While in the directory <CODE>ejabberd\src</CODE> run:
|
|
<PRE CLASS="verbatim">
|
|
configure.bat
|
|
nmake -f Makefile.win32
|
|
</PRE><LI CLASS="li-itemize">Edit the file <CODE>ejabberd\src\ejabberd.cfg</CODE> and run
|
|
<PRE CLASS="verbatim">
|
|
werl -s ejabberd -name ejabberd
|
|
</PRE></UL>
|
|
<!--TOC subsection Starting-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc12">2.4</A> <A NAME="start">Starting</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:start"></A>
|
|
|
|
|
|
Execute the following command to start <TT>ejabberd</TT>:
|
|
<PRE CLASS="verbatim">
|
|
erl -pa /var/lib/ejabberd/ebin -name ejabberd -s ejabberd
|
|
</PRE>or
|
|
<PRE CLASS="verbatim">
|
|
erl -pa /var/lib/ejabberd/ebin -sname ejabberd -s ejabberd
|
|
</PRE>In the latter case the Erlang node will be identified using only the first part
|
|
of the host name, i. e. other Erlang nodes outside this domain cannot contact
|
|
this node.<BR>
|
|
<BR>
|
|
Note that when using the above command, <TT>ejabberd</TT> will search for the
|
|
configuration file in the current directory and will use the current directory
|
|
for storing its user database and for logging.<BR>
|
|
<BR>
|
|
To specify the path to the configuration file, the log files and the Mnesia
|
|
database directory, you may use the following command:
|
|
<PRE CLASS="verbatim">
|
|
erl -pa /var/lib/ejabberd/ebin \
|
|
-sname ejabberd \
|
|
-s ejabberd \
|
|
-ejabberd config \"/etc/ejabberd/ejabberd.cfg\" \
|
|
log_path \"/var/log/ejabberd/ejabberd.log\" \
|
|
-sasl sasl_error_logger \{file,\"/var/log/ejabberd/sasl.log\"\} \
|
|
-mnesia dir \"/var/lib/ejabberd/spool\"
|
|
</PRE>
|
|
You can find other useful options in the Erlang manual page
|
|
(<TT>erl -man erl</TT>).<BR>
|
|
<BR>
|
|
To use more than 1024 connections, you should set the environment variable
|
|
<CODE>ERL_MAX_PORTS</CODE>:
|
|
<PRE CLASS="verbatim">
|
|
export ERL_MAX_PORTS=32000
|
|
</PRE>Note that with this value, <TT>ejabberd</TT> will use more memory (approximately 6 MB
|
|
more).<BR>
|
|
<BR>
|
|
To reduce memory usage, you may set the environment variable
|
|
<CODE>ERL_FULLSWEEP_AFTER</CODE>:
|
|
<PRE CLASS="verbatim">
|
|
export ERL_FULLSWEEP_AFTER=0
|
|
</PRE>But in this case <TT>ejabberd</TT> can start to work slower.<BR>
|
|
<BR>
|
|
<!--TOC section Basic Configuration-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc13">3</A> <A NAME="basicconfig">Basic Configuration</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:basicconfig"></A>
|
|
|
|
The configuration file will be loaded the first time you start <TT>ejabberd</TT>. The
|
|
content from this file will be parsed and stored in a database. Subsequently the
|
|
configuration will be loaded from the database and any commands in the
|
|
configuration file are appended to the entries in the database. The
|
|
configuration file contains a sequence of Erlang terms. Lines beginning with a
|
|
<TT>`%'</TT> sign are ignored. Each term is a tuple of which the first element is
|
|
the name of an option, and any further elements are that option's values. If the
|
|
configuration file do not contain for instance the `hosts' option, the old
|
|
host name(s) stored in the database will be used.<BR>
|
|
<BR>
|
|
You can override the old values stored in the database by adding next lines to
|
|
the configuration file:
|
|
<PRE CLASS="verbatim">
|
|
override_global.
|
|
override_local.
|
|
override_acls.
|
|
</PRE>With these lines the old global options, local options and ACLs will be removed
|
|
before new ones are added.<BR>
|
|
<BR>
|
|
<!--TOC subsection Host Names-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc14">3.1</A> <A NAME="hostnames">Host Names</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:hostnames"></A>
|
|
|
|
The option <TT>hosts</TT> defines a list containing one or more domains that
|
|
<TT>ejabberd</TT> will serve.<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Serving one domain:
|
|
<PRE CLASS="verbatim">
|
|
{hosts, ["example.org"]}.
|
|
</PRE><LI CLASS="li-itemize">Serving one domain, and backwards compatible with older <TT>ejabberd</TT>
|
|
versions:
|
|
<PRE CLASS="verbatim">
|
|
{host, "example.org"}.
|
|
</PRE><LI CLASS="li-itemize">Serving two domains:
|
|
<PRE CLASS="verbatim">
|
|
{hosts, ["example.net", "example.com"]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection Virtual Hosting-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc15">3.2</A> <A NAME="virtualhost">Virtual Hosting</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:virtualhost"></A>
|
|
|
|
Options can be defined separately for every virtual host using the
|
|
<TT>host_config</TT> option. It has the following
|
|
syntax:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, <hostname>, [<option>, <option>, ...]}.
|
|
</PRE>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Domain <TT>example.net</TT> is using the internal authentication method while
|
|
domain <TT>example.com</TT> is using the LDAP server running on the
|
|
domain <TT>localhost</TT> to perform authentication:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "example.net", [{auth_method, internal}]}.
|
|
|
|
{host_config, "example.com", [{auth_method, ldap},
|
|
{ldap_servers, ["localhost"]},
|
|
{ldap_uidattr, "uid"},
|
|
{ldap_rootdn, "dc=localdomain"},
|
|
{ldap_rootdn, "dc=example,dc=com"},
|
|
{ldap_password, ""}]}.
|
|
</PRE><LI CLASS="li-itemize">Domain <TT>example.net</TT> is using ODBC to perform authentication
|
|
while domain <TT>example.com</TT> is using the LDAP servers running on the domains
|
|
<TT>localhost</TT> and <TT>otherhost</TT>:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "example.net", [{auth_method, odbc},
|
|
{odbc_server, "DSN=ejabberd;UID=ejabberd;PWD=ejabberd"}]}.
|
|
|
|
{host_config, "example.com", [{auth_method, ldap},
|
|
{ldap_servers, ["localhost", "otherhost"]},
|
|
{ldap_uidattr, "uid"},
|
|
{ldap_rootdn, "dc=localdomain"},
|
|
{ldap_rootdn, "dc=example,dc=com"},
|
|
{ldap_password, ""}]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection Listened Sockets-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc16">3.3</A> <A NAME="listened">Listened Sockets</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:listened"></A>
|
|
|
|
The option <TT>listen</TT> defines for which addresses and ports <TT>ejabberd</TT>
|
|
will listen and what services will be run on them. Each element of the list is a
|
|
tuple with the following elements:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Port number.
|
|
<LI CLASS="li-itemize">Module that serves this port.
|
|
<LI CLASS="li-itemize">Options to this module.
|
|
</UL>
|
|
|
|
Currently next modules are implemented:
|
|
<BLOCKQUOTE CLASS="table"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
|
|
<TABLE BORDER=1 CELLSPACING=0 CELLPADDING=1>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP><TT>ejabberd_c2s</TT></TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Description</TD>
|
|
<TD VALIGN=top ALIGN=left>Handles c2s connections.</TD>
|
|
</TR>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP> </TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Options</TD>
|
|
<TD VALIGN=top ALIGN=left><TT>access</TT>, <TT>certfile</TT>, <TT>inet6</TT>,
|
|
<TT>ip</TT>, <TT>max_stanza_size</TT>, <TT>shaper</TT>, <TT>ssl</TT>,
|
|
<TT>tls</TT>, <TT>starttls</TT>, <TT>starttls_required</TT>,
|
|
<TT>zlib</TT></TD>
|
|
</TR>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP><TT>ejabberd_s2s_in</TT></TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Description</TD>
|
|
<TD VALIGN=top ALIGN=left>Handles incoming s2s
|
|
connections.</TD>
|
|
</TR>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP> </TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Options</TD>
|
|
<TD VALIGN=top ALIGN=left><TT>inet6</TT>, <TT>ip</TT>,
|
|
<TT>max_stanza_size</TT></TD>
|
|
</TR>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP><TT>ejabberd_service</TT></TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Description</TD>
|
|
<TD VALIGN=top ALIGN=left>Interacts with external
|
|
components (*).</TD>
|
|
</TR>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP> </TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Options</TD>
|
|
<TD VALIGN=top ALIGN=left><TT>access</TT>, <TT>hosts</TT>, <TT>inet6</TT>,
|
|
<TT>ip</TT>, <TT>shaper</TT></TD>
|
|
</TR>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP><TT>ejabberd_http</TT></TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Description</TD>
|
|
<TD VALIGN=top ALIGN=left>Handles incoming HTTP
|
|
connections.</TD>
|
|
</TR>
|
|
<TR><TD VALIGN=top ALIGN=left NOWRAP> </TD>
|
|
<TD VALIGN=top ALIGN=left NOWRAP>Options</TD>
|
|
<TD VALIGN=top ALIGN=left><TT>certfile</TT>, <TT>http_poll</TT>,
|
|
<TT>inet6</TT>, <TT>ip</TT>, <TT>tls</TT>, <TT>web_admin</TT></TD>
|
|
</TR></TABLE>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
(*) The mechanism for <A HREF="http://ejabberd.jabber.ru/tutorials-transports">external components</A> is defined in Jabber Component Protocol (<A HREF="http://www.jabber.org/jeps/jep-0114.html">JEP-0114</A>).<BR>
|
|
<BR>
|
|
The following options are available:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>{access, <access rule>}</TT></B><DD CLASS="dd-description"> This option defines
|
|
access to the port. The default value is <TT>all</TT>.
|
|
<DT CLASS="dt-description"><B><TT>{certfile, Path}</TT></B><DD CLASS="dd-description"> Path to a file containing the SSL certificate.
|
|
<DT CLASS="dt-description"><B><TT>{hosts, [Hostnames], [HostOptions]}</TT></B><DD CLASS="dd-description"> This option
|
|
defines one or more hostnames of connected services and enables you to
|
|
specify additional options including <TT>{password, Secret}</TT>.
|
|
<DT CLASS="dt-description"><B><TT>http_poll</TT></B><DD CLASS="dd-description">
|
|
This option enables HTTP Polling (<A HREF="http://www.jabber.org/jeps/jep-0025.html">JEP-0025</A>) support. HTTP Polling
|
|
enables access via HTTP requests to <TT>ejabberd</TT> from behind firewalls which
|
|
do not allow outgoing sockets on port 5222.<BR>
|
|
<BR>
|
|
If HTTP Polling is enabled, it will be available at
|
|
<CODE>http://server:port/http-poll/</CODE>. Be aware that support for HTTP Polling
|
|
is also needed in the Jabber client. Remark also that HTTP Polling can be
|
|
interesting to host a web-based Jabber client such as
|
|
<A HREF="http://jwchat.sourceforge.net/">JWChat</A> (there is a tutorial to
|
|
<A HREF="http://ejabberd.jabber.ru/jwchat">install JWChat</A> with
|
|
instructions for <TT>ejabberd</TT>).
|
|
<DT CLASS="dt-description"><B><TT>inet6</TT></B><DD CLASS="dd-description"> Set up the socket for IPv6.
|
|
<DT CLASS="dt-description"><B><TT>{ip, IPAddress}</TT></B><DD CLASS="dd-description"> This option specifies which network
|
|
interface to listen for. For example <CODE>{ip, {192, 168, 1, 1}}</CODE>.
|
|
<DT CLASS="dt-description"><B><TT>{max_stanza_size, Size}</TT></B><DD CLASS="dd-description"> This
|
|
option specifies an approximate maximum size in bytes of XML stanzas.
|
|
Approximate, because it is calculated with the precision of one block of
|
|
readed data. For example <CODE>{max_stanza_size, 65536}</CODE>. The default
|
|
value is <TT>infinity</TT>.
|
|
<DT CLASS="dt-description"><B><TT>{shaper, <access rule>}</TT></B><DD CLASS="dd-description"> This option defines a
|
|
shaper for the port (see section <A HREF="#sec:shapers">3.6</A>). The default value
|
|
is <TT>none</TT>.
|
|
<DT CLASS="dt-description"><B><TT>ssl</TT></B><DD CLASS="dd-description"> This option specifies that traffic on
|
|
the port will be encrypted using SSL. You should also set the
|
|
<TT>certfile</TT> option. It is recommended to use the <TT>tls</TT> option
|
|
instead.
|
|
<DT CLASS="dt-description"><B><TT>starttls</TT></B><DD CLASS="dd-description"> This option
|
|
specifies that STARTTLS encryption is available on connections to the port.
|
|
You should also set the <TT>certfile</TT> option.
|
|
<DT CLASS="dt-description"><B><TT>starttls_required</TT></B><DD CLASS="dd-description"> This option
|
|
specifies that STARTTLS encryption is required on connections to the port.
|
|
No unencrypted connections will be allowed. You should also set the
|
|
<TT>certfile</TT> option.
|
|
<DT CLASS="dt-description"><B><TT>tls</TT></B><DD CLASS="dd-description"> This option specifies that traffic on
|
|
the port will be encrypted using SSL immediately after connecting. You
|
|
should also set the <TT>certfile</TT> option.
|
|
<DT CLASS="dt-description"><B><TT>zlib</TT></B><DD CLASS="dd-description"> This
|
|
option specifies that Zlib stream compression (as defined in <A HREF="http://www.jabber.org/jeps/jep-0138.html">JEP-0138</A>)
|
|
is available on connections to the port. Client connections cannot use
|
|
stream compression and stream encryption simultaneously. Hence, if you
|
|
specify both <TT>tls</TT> (or <TT>ssl</TT>) and <TT>zlib</TT>, the latter
|
|
option will not affect connections (there will be no stream compression).
|
|
<DT CLASS="dt-description"><B><TT>web_admin</TT></B><DD CLASS="dd-description"> This option
|
|
enables the web interface for <TT>ejabberd</TT> administration which is available
|
|
at <CODE>http://server:port/admin/</CODE>. Login and password are the username and
|
|
password of one of the registered users who are granted access by the
|
|
`configure' access rule.
|
|
</DL>
|
|
In addition, the following options are available for s2s connections:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>{s2s_use_starttls, true|false}</TT></B><DD CLASS="dd-description">
|
|
This option defines whether to
|
|
use STARTTLS for s2s connections.
|
|
<DT CLASS="dt-description"><B><TT>{s2s_certfile, Path}</TT></B><DD CLASS="dd-description"> Path to a
|
|
file containing a SSL certificate.
|
|
<DT CLASS="dt-description"><B><TT>{domain_certfile, Domain, Path}</TT></B><DD CLASS="dd-description"> Path
|
|
to the file containing the SSL certificate for the specified domain.
|
|
</DL>
|
|
For instance, the following configuration defines that:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
c2s connections are listened for on port 5222 and 5223 (SSL) and denied
|
|
for the user called `<TT>bad</TT>'.
|
|
<LI CLASS="li-itemize">s2s connections are listened for on port 5269 with STARTTLS for secured
|
|
traffic enabled.
|
|
<LI CLASS="li-itemize">Port 5280 is serving the web interface and the HTTP Polling service. Note
|
|
that it is also possible to serve them on different ports. The second
|
|
example in section <A HREF="#sec:webinterface">7.1</A> shows how exactly this can be done.
|
|
<LI CLASS="li-itemize">All users except for the administrators have a traffic of limit
|
|
1,000 Bytes/second
|
|
<LI CLASS="li-itemize">The
|
|
<A HREF="http://ejabberd.jabber.ru/pyaimt">AIM transport</A>
|
|
<TT>aim.example.org</TT> is connected to port 5233 with password
|
|
`<TT>aimsecret</TT>'.
|
|
<LI CLASS="li-itemize">The ICQ transport JIT (<TT>icq.example.org</TT> and
|
|
<TT>sms.example.org</TT>) is connected to port 5234 with password
|
|
`<TT>jitsecret</TT>'.
|
|
<LI CLASS="li-itemize">The
|
|
<A HREF="http://ejabberd.jabber.ru/pymsnt">MSN transport</A>
|
|
<TT>msn.example.org</TT> is connected to port 5235 with password
|
|
`<TT>msnsecret</TT>'.
|
|
<LI CLASS="li-itemize">The
|
|
<A HREF="http://ejabberd.jabber.ru/yahoo-transport-2">Yahoo! transport</A>
|
|
<TT>yahoo.example.org</TT> is connected to port 5236 with password
|
|
`<TT>yahoosecret</TT>'.
|
|
<LI CLASS="li-itemize">The <A HREF="http://ejabberd.jabber.ru/jabber-gg-transport">Gadu-Gadu transport</A> <TT>gg.example.org</TT> is
|
|
connected to port 5237 with password `<TT>ggsecret</TT>'.
|
|
<LI CLASS="li-itemize">The
|
|
<A HREF="http://ejabberd.jabber.ru/jmc">Jabber Mail Component</A>
|
|
<TT>jmc.example.org</TT> is connected to port 5238 with password
|
|
`<TT>jmcsecret</TT>'.
|
|
</UL>
|
|
<PRE CLASS="verbatim">
|
|
{acl, blocked, {user, "bad"}}.
|
|
{access, c2s, [{deny, blocked},
|
|
{allow, all}]}.
|
|
{shaper, normal, {maxrate, 1000}}.
|
|
{access, c2s_shaper, [{none, admin},
|
|
{normal, all}]}.
|
|
{listen,
|
|
[{5222, ejabberd_c2s, [{access, c2s}, {shaper, c2s_shaper}]},
|
|
{5223, ejabberd_c2s, [{access, c2s},
|
|
ssl, {certfile, "/path/to/ssl.pem"}]},
|
|
{5269, ejabberd_s2s_in, []},
|
|
{5280, ejabberd_http, [http_poll, web_admin]},
|
|
{5233, ejabberd_service, [{host, "aim.example.org",
|
|
[{password, "aimsecret"}]}]},
|
|
{5234, ejabberd_service, [{hosts, ["icq.example.org", "sms.example.org"],
|
|
[{password, "jitsecret"}]}]},
|
|
{5235, ejabberd_service, [{host, "msn.example.org",
|
|
[{password, "msnsecret"}]}]},
|
|
{5236, ejabberd_service, [{host, "yahoo.example.org",
|
|
[{password, "yahoosecret"}]}]},
|
|
{5237, ejabberd_service, [{host, "gg.example.org",
|
|
[{password, "ggsecret"}]}]},
|
|
{5238, ejabberd_service, [{host, "jmc.example.org",
|
|
[{password, "jmcsecret"}]}]}
|
|
]
|
|
}.
|
|
{s2s_use_starttls, true}.
|
|
{s2s_certfile, "/path/to/ssl.pem"}.
|
|
</PRE>Note, that for jabberd 1.4- or WPJabber-based
|
|
services you have to make the transports log and do XDB by themselves:
|
|
<PRE CLASS="verbatim">
|
|
<!--
|
|
You have to add elogger and rlogger entries here when using ejabberd.
|
|
In this case the transport will do the logging.
|
|
-->
|
|
|
|
<log id='logger'>
|
|
<host/>
|
|
<logtype/>
|
|
<format>%d: [%t] (%h): %s</format>
|
|
<file>/var/log/jabber/service.log</file>
|
|
</log>
|
|
|
|
<!--
|
|
Some Jabber server implementations do not provide
|
|
XDB services (for example, jabberd2 and ejabberd).
|
|
xdb_file.so is loaded in to handle all XDB requests.
|
|
-->
|
|
|
|
<xdb id="xdb">
|
|
<host/>
|
|
<load>
|
|
<!-- this is a lib of wpjabber or jabberd -->
|
|
<xdb_file>/usr/lib/jabber/xdb_file.so</xdb_file>
|
|
</load>
|
|
<xdb_file xmlns="jabber:config:xdb_file">
|
|
<spool><jabberd:cmdline flag='s'>/var/spool/jabber</jabberd:cmdline></spool>
|
|
</xdb_file>
|
|
</xdb>
|
|
</PRE>
|
|
<!--TOC subsection Authentication-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc17">3.4</A> <A NAME="auth">Authentication</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:auth"></A>
|
|
|
|
The option <TT>auth_method</TT> defines the authentication method that is used
|
|
for user authentication:
|
|
<PRE CLASS="verbatim">
|
|
{auth_method, [<method>]}.
|
|
</PRE>
|
|
The following authentication methods are supported by <TT>ejabberd</TT>:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
internal (default) — See section <A HREF="#sec:internalauth">3.4.1</A>.
|
|
<LI CLASS="li-itemize">external — There are <A HREF="http://ejabberd.jabber.ru/extauth">some
|
|
example authentication scripts</A>.
|
|
<LI CLASS="li-itemize">ldap — See section <A HREF="#sec:ldap">4.5</A>.
|
|
<LI CLASS="li-itemize">odbc — See section <A HREF="#sec:mysql">4.1</A>, <A HREF="#sec:pgsql">4.3</A>,
|
|
<A HREF="#sec:mssql">4.2</A> and <A HREF="#sec:odbc">4.4</A>.
|
|
<LI CLASS="li-itemize">anonymous — See section <A HREF="#sec:saslanonymous">3.4.2</A>.
|
|
</UL>
|
|
<!--TOC subsubsection Internal-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc18">3.4.1</A> <A NAME="internalauth">Internal</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:internalauth"></A>
|
|
|
|
<TT>ejabberd</TT> uses its internal Mnesia database as the default authentication method.
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
<TT>auth_method</TT>: The value <TT>internal</TT> will enable the internal
|
|
authentication method.
|
|
</UL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
To use internal authentication on <TT>example.org</TT> and LDAP
|
|
authentication on <TT>example.net</TT>:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "example.org", [{auth_method, [internal]}]}.
|
|
{host_config, "example.net", [{auth_method, [ldap]}]}.
|
|
</PRE><LI CLASS="li-itemize">To use internal authentication on all virtual hosts:
|
|
<PRE CLASS="verbatim">
|
|
{auth_method, internal}.
|
|
</PRE></UL>
|
|
<!--TOC subsubsection SASL Anonymous and Anonymous Login-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc19">3.4.2</A> <A NAME="saslanonymous">SASL Anonymous and Anonymous Login</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:saslanonymous"></A>
|
|
|
|
The anonymous authentication method can be configured with the following
|
|
options. Remember that you can use the <TT>host_config</TT> option to set virtual
|
|
host specific options (see section <A HREF="#sec:virtualhost">3.2</A>). Note that there also
|
|
is a detailed tutorial regarding <A HREF="http://support.process-one.net/doc/display/MESSENGER/Anonymous+users+support">SASL
|
|
Anonymous and anonymous login configuration</A>.
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
<TT>auth_method</TT>: The value <TT>anonymous</TT> will enable the anonymous
|
|
authentication method.
|
|
<LI CLASS="li-itemize"><TT>allow_multiple_connections</TT>: This value for this option can be
|
|
either <TT>true</TT> or <TT>false</TT> and is only used when the anonymous mode is
|
|
enabled. Setting it to <TT>true</TT> means that the same username can be taken
|
|
multiple times in anonymous login mode if different resource are used to
|
|
connect. This option is only useful in very special occasions. The default
|
|
value is <TT>false</TT>.
|
|
<LI CLASS="li-itemize"><TT>anonymous_protocol</TT>: This option can take three values:
|
|
<TT>sasl_anon</TT>, <TT>login_anon</TT> or <TT>both</TT>. <TT>sasl_anon</TT> means
|
|
that the SASL Anonymous method will be used. <TT>login_anon</TT> means that the
|
|
anonymous login method will be used. <TT>both</TT> means that SASL Anonymous and
|
|
login anonymous are both enabled.
|
|
</UL>
|
|
Those options are defined for each virtual host with the <TT>host_config</TT>
|
|
parameter (see section <A HREF="#sec:virtualhost">3.2</A>).<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
To enable anonymous login on all virtual hosts:
|
|
<PRE CLASS="verbatim">
|
|
{auth_method, [anonymous]}.
|
|
{anonymous_protocol, login_anon}.
|
|
</PRE><LI CLASS="li-itemize">Similar as previous example, but limited to <TT>public.example.org</TT>:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [anonymous]},
|
|
{anonymous_protocol, login_anon}]}.
|
|
</PRE><LI CLASS="li-itemize">To enable anonymous login and internal authentication on a virtual host:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [anonymous,internal]},
|
|
{anonymous_protocol, login_anon}]}.
|
|
</PRE><LI CLASS="li-itemize">To enable SASL Anonymous on a virtual host:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [anonymous]},
|
|
{anonymous_protocol, sasl_anon}]}.
|
|
</PRE><LI CLASS="li-itemize">To enable SASL Anonymous and anonymous login on a virtual host:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [anonymous]},
|
|
{anonymous_protocol, both}]}.
|
|
</PRE><LI CLASS="li-itemize">To enable SASL Anonymous, anonymous login, and internal authentication on
|
|
a virtual host:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [anonymous,internal]},
|
|
{anonymous_protocol, both}]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection Access Rules-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc20">3.5</A> <A NAME="accessrules">Access Rules</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:accessrules"></A>
|
|
|
|
Access control in <TT>ejabberd</TT> is performed via Access Control Lists (ACLs). The
|
|
declarations of ACLs in the configuration file have the following syntax:
|
|
<PRE CLASS="verbatim">
|
|
{acl, <aclname>, {<acltype>, ...}}.
|
|
</PRE>
|
|
<TT><acltype></TT> can be one of the following:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>all</TT></B><DD CLASS="dd-description"> Matches all JIDs. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, all, all}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{user, <username>}</TT></B><DD CLASS="dd-description"> Matches the user with the name
|
|
<TT><username></TT> at the first virtual host. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, admin, {user, "yozhik"}}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{user, <username>, <server>}</TT></B><DD CLASS="dd-description"> Matches the user with the JID
|
|
<TT><username>@<server></TT> and any resource. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, admin, {user, "yozhik", "example.org"}}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{server, <server>}</TT></B><DD CLASS="dd-description"> Matches any JID from server
|
|
<TT><server></TT>. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, exampleorg, {server, "example.org"}}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{user_regexp, <regexp>}</TT></B><DD CLASS="dd-description"> Matches any local user with a name that
|
|
matches <TT><regexp></TT> at the first virtual host. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, tests, {user, "^test[0-9]*$"}}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{user_regexp, <regexp>, <server>}</TT></B><DD CLASS="dd-description"> Matches any user with a name
|
|
that matches <TT><regexp></TT> at server <TT><server></TT>. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, tests, {user, "^test", "example.org"}}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{server_regexp, <regexp>}</TT></B><DD CLASS="dd-description"> Matches any JID from the server that
|
|
matches <TT><regexp></TT>. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, icq, {server, "^icq\\."}}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{node_regexp, <user_regexp>, <server_regexp>}</TT></B><DD CLASS="dd-description"> Matches any user
|
|
with a name that matches <TT><user_regexp></TT> at any server that matches
|
|
<TT><server_regexp></TT>. Example:
|
|
<PRE CLASS="verbatim">
|
|
{acl, yohzik, {node_regexp, "^yohzik$", "^example.(com|org)$"}}.
|
|
</PRE><DT CLASS="dt-description"><B><TT>{user_glob, <glob>}</TT></B><DD CLASS="dd-description">
|
|
<DT CLASS="dt-description"><B><TT>{user_glob, <glob>, <server>}</TT></B><DD CLASS="dd-description">
|
|
<DT CLASS="dt-description"><B><TT>{server_glob, <glob>}</TT></B><DD CLASS="dd-description">
|
|
<DT CLASS="dt-description"><B><TT>{node_glob, <user_glob>, <server_glob>}</TT></B><DD CLASS="dd-description"> This is the same as
|
|
above. However, it uses shell glob patterns instead of regexp. These patterns
|
|
can have the following special characters:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>*</TT></B><DD CLASS="dd-description"> matches any string including the null string.
|
|
<DT CLASS="dt-description"><B><TT>?</TT></B><DD CLASS="dd-description"> matches any single character.
|
|
<DT CLASS="dt-description"><B><TT>[...]</TT></B><DD CLASS="dd-description"> matches any of the enclosed characters. Character
|
|
ranges are specified by a pair of characters separated by a <TT>`-'</TT>.
|
|
If the first character after <TT>`['</TT> is a <TT>`!'</TT>, any
|
|
character not enclosed is matched.
|
|
</DL>
|
|
</DL>
|
|
The following ACLs are pre-defined:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>all</TT></B><DD CLASS="dd-description"> Matches any JID.
|
|
<DT CLASS="dt-description"><B><TT>none</TT></B><DD CLASS="dd-description"> Matches no JID.
|
|
</DL>
|
|
An entry allowing or denying access to different services looks similar to
|
|
this:
|
|
<PRE CLASS="verbatim">
|
|
{access, <accessname>, [{allow, <aclname>},
|
|
{deny, <aclname>},
|
|
...
|
|
]}.
|
|
</PRE>When a JID is checked to have access to <TT><accessname></TT>, the server
|
|
sequentially checks if that JID mathes any of the ACLs that are named in the
|
|
second elements of the tuples in the list. If it matches, the first element of
|
|
the first matched tuple is returned, otherwise the value `<TT>deny</TT>' is
|
|
returned.<BR>
|
|
<BR>
|
|
Example:
|
|
<PRE CLASS="verbatim">
|
|
{access, configure, [{allow, admin}]}.
|
|
{access, something, [{deny, badmans},
|
|
{allow, all}]}.
|
|
</PRE>
|
|
The following access rules are pre-defined:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>all</TT></B><DD CLASS="dd-description"> Always returns the value `<TT>allow</TT>'.
|
|
<DT CLASS="dt-description"><B><TT>none</TT></B><DD CLASS="dd-description"> Always returns the value `<TT>deny</TT>'.
|
|
</DL>
|
|
<!--TOC subsection Shapers-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc21">3.6</A> <A NAME="shapers">Shapers</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:shapers"></A>
|
|
|
|
Shapers enable you to limit connection traffic. The syntax of
|
|
shapers is like this:
|
|
<PRE CLASS="verbatim">
|
|
{shaper, <shapername>, <kind>}.
|
|
</PRE>Currently only one kind of shaper called <TT>maxrate</TT> is available. It has the
|
|
following syntax:
|
|
<PRE CLASS="verbatim">
|
|
{maxrate, <rate>}
|
|
</PRE>where <TT><rate></TT> stands for the maximum allowed incomig rate in bytes per
|
|
second.<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
To define a shaper named `<TT>normal</TT>' with traffic speed limited to
|
|
1,000 bytes/second:
|
|
<PRE CLASS="verbatim">
|
|
{shaper, normal, {maxrate, 1000}}.
|
|
</PRE><LI CLASS="li-itemize">To define a shaper named `<TT>fast</TT>' with traffic speed limited to
|
|
50,000 bytes/second:
|
|
<PRE CLASS="verbatim">
|
|
{shaper, fast, {maxrate, 50000}}.
|
|
</PRE></UL>
|
|
<!--TOC subsection Limiting Opened Sessions-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc22">3.7</A> Limiting Opened Sessions</H3><!--SEC END -->
|
|
|
|
<A NAME="sec:configmaxsessions"></A>
|
|
|
|
This option specifies the maximum number of sessions (authenticated
|
|
connections) per user. If a user tries to open more sessions by using different
|
|
resources, the first opened session will be disconnected. The error
|
|
<TT>session replaced</TT> will be sent to the disconnected session. The value
|
|
for this option can be either a number, or <TT>infinity</TT>. The default
|
|
value is <TT>10</TT>.<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
To limit the number of sessions per user to 10 on all virtual
|
|
hosts:
|
|
<PRE CLASS="verbatim">
|
|
{max_user_sessions, 10}.
|
|
</PRE><LI CLASS="li-itemize">This option can be defined per virtual host (see
|
|
section <A HREF="#sec:virtualhost">3.2</A>). In next example the number of
|
|
sessions per user on the first host is six, while there is no limit on the
|
|
second host:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "example.net", [{max_user_sessions, 6}]}.
|
|
{host_config, "example.com", [{max_user_sessions, infinity}]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection Default Language-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc23">3.8</A> <A NAME="language">Default Language</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:language"></A>
|
|
|
|
The option <TT>language</TT> defines the default language of server strings that
|
|
can be seen by Jabber clients. If a Jabber client do not support
|
|
<TT>xml:lang</TT>, the specified language is used. The default value is
|
|
<TT>en</TT>. In order to take effect there must be a translation file
|
|
<TT><language>.msg</TT> in <TT>ejabberd</TT>'s <TT>msgs</TT> directory.<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
To set Russian as default language:
|
|
<PRE CLASS="verbatim">
|
|
{language, "ru"}.
|
|
</PRE><LI CLASS="li-itemize">To set Spanish as default language:
|
|
<PRE CLASS="verbatim">
|
|
{language, "es"}.
|
|
</PRE></UL>
|
|
<!--TOC section Database Configuration-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc24">4</A> <A NAME="database">Database Configuration</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:database"></A>
|
|
|
|
|
|
<TT>ejabberd</TT> uses its internal Mnesia database by default. However, it is
|
|
possible to use a relational database or an LDAP server to store persistant,
|
|
long-living data. <TT>ejabberd</TT> is very flexible: you can configure different
|
|
authentication methods for different virtual hosts, you can configure different
|
|
authentication mechanisms for the same virtual host (fallback), you can set
|
|
different storage systems for modules, and so forth.<BR>
|
|
<BR>
|
|
The following databases are supported by <TT>ejabberd</TT>:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
<A HREF="http://www.microsoft.com/sql/">Microsoft SQL Server</A>
|
|
<LI CLASS="li-itemize"><A HREF="http://www.erlang.org/doc/doc-5.5.1/lib/mnesia-4.3.2/doc/">Mnesia</A>
|
|
<LI CLASS="li-itemize"><A HREF="http://mysql.com/">MySQL</A>
|
|
<LI CLASS="li-itemize"><A HREF="http://en.wikipedia.org/wiki/Open_Database_Connectivity">Any ODBC compatible database</A>
|
|
<LI CLASS="li-itemize"><A HREF="http://www.postgresql.org/">PostgreSQL</A>
|
|
</UL>
|
|
The following LDAP servers are tested with <TT>ejabberd</TT>:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
<A HREF="http://www.microsoft.com/activedirectory/">Active Directory</A>
|
|
(see section <A HREF="#sec:ad">4.5.3</A>)
|
|
<LI CLASS="li-itemize"><A HREF="http://www.openldap.org/">OpenLDAP</A>
|
|
<LI CLASS="li-itemize">Normally any LDAP compatible server should work; inform us about your
|
|
success with a not-listed server so that we can list it here.
|
|
</UL>
|
|
<!--TOC subsection MySQL-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc25">4.1</A> <A NAME="mysql">MySQL</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:mysql"></A>
|
|
|
|
Although this section will describe <TT>ejabberd</TT>'s configuration when you want to
|
|
use the native MySQL driver, it does not describe MySQL's installation and
|
|
database creation. Check the MySQL documentation and the tutorial <A HREF="http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver">Using ejabberd with MySQL native driver</A> for information regarding these topics.
|
|
Note that the tutorial contains information about <TT>ejabberd</TT>'s configuration
|
|
which is duplicate to this section.<BR>
|
|
<BR>
|
|
Moreover, the file mysql.sql in the directory src/odbc might be interesting for
|
|
you. This file contains the ejabberd schema for MySQL. At the end of the file
|
|
you can find information to update your database schema.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Driver Compilation-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc26">4.1.1</A> <A NAME="compilemysql">Driver Compilation</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:compilemysql"></A>
|
|
|
|
You can skip this step if you installed <TT>ejabberd</TT> using a binary installer or
|
|
if the binary packages of <TT>ejabberd</TT> you are using include support for MySQL.
|
|
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
|
|
First, install the <A HREF="http://support.process-one.net/doc/display/CONTRIBS/Yxa">Erlang
|
|
MySQL library</A>. Make sure the compiled files are in your Erlang path; you can
|
|
put them for example in the same directory as your ejabberd .beam files.
|
|
<LI CLASS="li-enumerate">Then, configure and install <TT>ejabberd</TT> with ODBC support enabled (this is
|
|
also needed for native MySQL support!). This can be done, by using next
|
|
commands:
|
|
<PRE CLASS="verbatim">
|
|
./configure --enable-odbc && make install
|
|
</PRE></OL>
|
|
<!--TOC subsubsection Authentication-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc27">4.1.2</A> <A NAME="mysqlauth">Authentication</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:mysqlauth"></A>
|
|
|
|
The option value name may be misleading, as the <TT>auth_method</TT> name is used
|
|
for access to a relational database through ODBC, as well as through the native
|
|
MySQL interface. Anyway, the first configuration step is to define the odbc
|
|
<TT>auth_method</TT>. For example:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [odbc]}]}.
|
|
</PRE>
|
|
The actual database access is defined in the option <TT>odbc_server</TT>. Its
|
|
value is used to define if we want to use ODBC, or one of the two native
|
|
interface available, PostgreSQL or MySQL.<BR>
|
|
<BR>
|
|
To use the native MySQL interface, you can pass a tuple of the following form as
|
|
parameter:
|
|
<PRE CLASS="verbatim">
|
|
{mysql, "Server", "Database", "Username", "Password"}
|
|
</PRE>
|
|
<TT>mysql</TT> is a keyword that should be kept as is. For example:
|
|
<PRE CLASS="verbatim">
|
|
{odbc_server, {mysql, "localhost", "test", "root", "password"}}.
|
|
</PRE>
|
|
<!--TOC subsubsection Storage-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc28">4.1.3</A> <A NAME="mysqlstorage">Storage</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:mysqlstorage"></A>
|
|
|
|
MySQL also can be used to store information into from several <TT>ejabberd</TT>
|
|
modules. See section <A HREF="#sec:modoverview">5.1</A> to see which modules have a version
|
|
with the `_odbc'. This suffix indicates that the module can be used with
|
|
relational databases like MySQL. To enable storage to your database, just make
|
|
sure that your database is running well (see previous sections), and replace the
|
|
suffix-less or ldap module variant with the odbc module variant. Keep in mind
|
|
that you cannot have several variants of the same module loaded!<BR>
|
|
<BR>
|
|
<!--TOC subsection Microsoft SQL Server-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc29">4.2</A> <A NAME="mssql">Microsoft SQL Server</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:mssql"></A>
|
|
|
|
Although this section will describe <TT>ejabberd</TT>'s configuration when you want to
|
|
use Microsoft SQL Server, it does not describe Microsoft SQL Server's
|
|
installation and database creation. Check the MySQL documentation and the
|
|
tutorial <A HREF="http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver">Using ejabberd with MySQL native driver</A> for information regarding these topics.
|
|
Note that the tutorial contains information about <TT>ejabberd</TT>'s configuration
|
|
which is duplicate to this section.<BR>
|
|
<BR>
|
|
Moreover, the file mssql.sql in the directory src/odbc might be interesting for
|
|
you. This file contains the ejabberd schema for Microsoft SQL Server. At the end
|
|
of the file you can find information to update your database schema.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Driver Compilation-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc30">4.2.1</A> <A NAME="compilemssql">Driver Compilation</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:compilemssql"></A>
|
|
|
|
You can skip this step if you installed <TT>ejabberd</TT> using a binary installer or
|
|
if the binary packages of <TT>ejabberd</TT> you are using include support for ODBC.<BR>
|
|
<BR>
|
|
If you want to use Microsoft SQL Server with ODBC, you need to configure,
|
|
compile and install <TT>ejabberd</TT> with support for ODBC and Microsoft SQL Server
|
|
enabled. This can be done, by using next commands:
|
|
<PRE CLASS="verbatim">
|
|
./configure --enable-odbc --enable-mssql && make install
|
|
</PRE>
|
|
<!--TOC subsubsection Authentication-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc31">4.2.2</A> <A NAME="mssqlauth">Authentication</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:mssqlauth"></A>
|
|
|
|
The configuration of Microsoft SQL Server is the same as the configuration of
|
|
ODBC compatible serers (see section <A HREF="#sec:odbcauth">4.4.2</A>).<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Storage-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc32">4.2.3</A> <A NAME="mssqlstorage">Storage</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:mssqlstorage"></A>
|
|
|
|
Microsoft SQL Server also can be used to store information into from several
|
|
<TT>ejabberd</TT> modules. See section <A HREF="#sec:modoverview">5.1</A> to see which modules have
|
|
a version with the `_odbc'. This suffix indicates that the module can be used
|
|
with relational databases like Microsoft SQL Server. To enable storage to your
|
|
database, just make sure that your database is running well (see previous
|
|
sections), and replace the suffix-less or ldap module variant with the odbc
|
|
module variant. Keep in mind that you cannot have several variants of the same
|
|
module loaded!<BR>
|
|
<BR>
|
|
<!--TOC subsection PostgreSQL-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc33">4.3</A> <A NAME="pgsql">PostgreSQL</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:pgsql"></A>
|
|
|
|
Although this section will describe <TT>ejabberd</TT>'s configuration when you want to
|
|
use the native PostgreSQL driver, it does not describe PostgreSQL's installation
|
|
and database creation. Check the PostgreSQL documentation and the tutorial <A HREF="http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver">Using ejabberd with MySQL native driver</A> for information regarding these topics.
|
|
Note that the tutorial contains information about <TT>ejabberd</TT>'s configuration
|
|
which is duplicate to this section.<BR>
|
|
<BR>
|
|
Also the file pg.sql in the directory src/odbc might be interesting for you.
|
|
This file contains the ejabberd schema for PostgreSQL. At the end of the file
|
|
you can find information to update your database schema.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Driver Compilation-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc34">4.3.1</A> <A NAME="compilepgsql">Driver Compilation</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:compilepgsql"></A>
|
|
|
|
You can skip this step if you installed <TT>ejabberd</TT> using a binary installer or
|
|
if the binary packages of <TT>ejabberd</TT> you are using include support for
|
|
PostgreSQL.
|
|
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
|
|
First, install the Erlang PgSQL library from
|
|
<A HREF="http://jungerl.sourceforge.net/">Jungerl</A>. Make sure the compiled
|
|
files are in your Erlang path; you can put them for example in the same
|
|
directory as your ejabberd .beam files.
|
|
<LI CLASS="li-enumerate">Then, configure, compile and install <TT>ejabberd</TT> with ODBC support enabled
|
|
(this is also needed for native PostgreSQL support!). This can be done, by
|
|
using next commands:
|
|
<PRE CLASS="verbatim">
|
|
./configure --enable-odbc && make install
|
|
</PRE></OL>
|
|
<!--TOC subsubsection Authentication-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc35">4.3.2</A> <A NAME="pgsqlauth">Authentication</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:pgsqlauth"></A>
|
|
|
|
The option value name may be misleading, as the <TT>auth_method</TT> name is used
|
|
for access to a relational database through ODBC, as well as through the native
|
|
PostgreSQL interface. Anyway, the first configuration step is to define the odbc
|
|
<TT>auth_method</TT>. For example:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [odbc]}]}.
|
|
</PRE>
|
|
The actual database access is defined in the option <TT>odbc_server</TT>. Its
|
|
value is used to define if we want to use ODBC, or one of the two native
|
|
interface available, PostgreSQL or MySQL.<BR>
|
|
<BR>
|
|
To use the native PostgreSQL interface, you can pass a tuple of the following
|
|
form as parameter:
|
|
<PRE CLASS="verbatim">
|
|
{pgsql, "Server", "Database", "Username", "Password"}
|
|
</PRE>
|
|
<TT>pgsql</TT> is a keyword that should be kept as is. For example:
|
|
<PRE CLASS="verbatim">
|
|
{odbc_server, {pgsql, "localhost", "database", "ejabberd", "password"}}.
|
|
</PRE>
|
|
<!--TOC subsubsection Storage-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc36">4.3.3</A> <A NAME="pgsqlstorage">Storage</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:pgsqlstorage"></A>
|
|
|
|
PostgreSQL also can be used to store information into from several <TT>ejabberd</TT>
|
|
modules. See section <A HREF="#sec:modoverview">5.1</A> to see which modules have a version
|
|
with the `_odbc'. This suffix indicates that the module can be used with
|
|
relational databases like PostgreSQL. To enable storage to your database, just
|
|
make sure that your database is running well (see previous sections), and
|
|
replace the suffix-less or ldap module variant with the odbc module variant.
|
|
Keep in mind that you cannot have several variants of the same module loaded!<BR>
|
|
<BR>
|
|
<!--TOC subsection ODBC Compatible-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc37">4.4</A> <A NAME="odbc">ODBC Compatible</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:odbc"></A>
|
|
|
|
Although this section will describe <TT>ejabberd</TT>'s configuration when you want to
|
|
use the ODBC driver, it does not describe the installation and database creation
|
|
of your database. Check the documentation of your database. The tutorial <A HREF="http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver">Using ejabberd with MySQL native driver</A> also can help you. Note that the tutorial
|
|
contains information about <TT>ejabberd</TT>'s configuration which is duplicate to
|
|
this section.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Compilation-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc38">4.4.1</A> <A NAME="compileodbc">Compilation</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:compileodbc"></A>
|
|
You can skip this step if you installed <TT>ejabberd</TT> using a binary installer or
|
|
if the binary packages of <TT>ejabberd</TT> you are using include support for
|
|
ODBC.
|
|
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
|
|
First, install the <A HREF="http://support.process-one.net/doc/display/CONTRIBS/Yxa">Erlang
|
|
MySQL library</A>. Make sure the compiled files are in your Erlang path; you can
|
|
put them for example in the same directory as your ejabberd .beam files.
|
|
<LI CLASS="li-enumerate">Then, configure, compile and install <TT>ejabberd</TT> with ODBC support
|
|
enabled. This can be done, by using next commands:
|
|
<PRE CLASS="verbatim">
|
|
./configure --enable-odbc && make install
|
|
</PRE></OL>
|
|
<!--TOC subsubsection Authentication-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc39">4.4.2</A> <A NAME="odbcauth">Authentication</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:odbcauth"></A>
|
|
|
|
The first configuration step is to define the odbc <TT>auth_method</TT>. For
|
|
example:
|
|
<PRE CLASS="verbatim">
|
|
{host_config, "public.example.org", [{auth_method, [odbc]}]}.
|
|
</PRE>
|
|
The actual database access is defined in the option <TT>odbc_server</TT>. Its
|
|
value is used to defined if we want to use ODBC, or one of the two native
|
|
interface available, PostgreSQL or MySQL.<BR>
|
|
<BR>
|
|
To use a relational database through ODBC, you can pass the ODBC connection
|
|
string as <TT>odbc_server</TT> parameter. For example:
|
|
<PRE CLASS="verbatim">
|
|
{odbc_server, "DSN=database;UID=ejabberd;PWD=password"}.
|
|
</PRE>
|
|
<!--TOC subsubsection Storage-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc40">4.4.3</A> <A NAME="odbcstorage">Storage</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:odbcstorage"></A>
|
|
|
|
An ODBC compatible database also can be used to store information into from
|
|
several <TT>ejabberd</TT> modules. See section <A HREF="#sec:modoverview">5.1</A> to see which
|
|
modules have a version with the `_odbc'. This suffix indicates that the module
|
|
can be used with ODBC compatible relational databases. To enable storage to your
|
|
database, just make sure that your database is running well (see previous
|
|
sections), and replace the suffix-less or ldap module variant with the odbc
|
|
module variant. Keep in mind that you cannot have several variants of the same
|
|
module loaded!<BR>
|
|
<BR>
|
|
<!--TOC subsection LDAP-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc41">4.5</A> <A NAME="ldap">LDAP</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:ldap"></A>
|
|
|
|
<TT>ejabberd</TT> has built-in LDAP support. You can authenticate users against LDAP
|
|
server and use LDAP directory as vCard storage. Shared rosters are not supported
|
|
yet.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Connection-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc42">4.5.1</A> <A NAME="ldapconnection">Connection</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:ldapconnection"></A>
|
|
Parameters:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>ldap_server</TT></B><DD CLASS="dd-description"> IP address or dns name of your
|
|
LDAP server. This option is required.
|
|
<DT CLASS="dt-description"><B><TT>ldap_port</TT></B><DD CLASS="dd-description"> Port to connect to your LDAP server.
|
|
The default value is 389.
|
|
<DT CLASS="dt-description"><B><TT>ldap_rootdn</TT></B><DD CLASS="dd-description"> Bind DN. The default value
|
|
is <TT>""</TT> which means `anonymous connection'.
|
|
<DT CLASS="dt-description"><B><TT>ldap_password</TT></B><DD CLASS="dd-description"> Bind password. The default
|
|
value is <TT>""</TT>.
|
|
</DL>
|
|
Example:
|
|
<PRE CLASS="verbatim">
|
|
{auth_method, ldap}.
|
|
{ldap_servers, ["ldap.example.org"]}.
|
|
{ldap_port, 389}.
|
|
{ldap_rootdn, "cn=Manager,dc=domain,dc=org"}.
|
|
{ldap_password, "secret"}.
|
|
</PRE>
|
|
Note that current LDAP implementation does not support SSL secured communication
|
|
and SASL authentication.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Authentication-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc43">4.5.2</A> <A NAME="ldapauth">Authentication</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:ldapauth"></A>
|
|
You can authenticate users against an LDAP directory. Available options are:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>ldap_base</TT></B><DD CLASS="dd-description">LDAP base directory which stores users
|
|
accounts. This option is required.
|
|
<DT CLASS="dt-description"><B><TT>ldap_uidattr</TT></B><DD CLASS="dd-description">LDAP attribute which holds
|
|
the user's part of a JID. The default value is <TT>"uid"</TT>.
|
|
<DT CLASS="dt-description"><B><TT>ldap_uidattr_format</TT></B><DD CLASS="dd-description">Format of the
|
|
<TT>ldap_uidattr</TT> variable. The format <EM>must</EM> contain one and only one
|
|
pattern variable <TT>"%u"</TT> which will be replaced by the user's part of a
|
|
JID. For example, <TT>"%u@example.org"</TT>. The default value is <TT>"%u"</TT>.
|
|
<DT CLASS="dt-description"><B><TT>ldap_filter</TT></B><DD CLASS="dd-description">
|
|
<A HREF="http://www.faqs.org/rfcs/rfc2254.html">RFC 2254</A> LDAP filter. The
|
|
default is <TT>none</TT>. Example:
|
|
<TT>"(&(objectClass=shadowAccount)(memberOf=Jabber Users))"</TT>. Please, do
|
|
not forget to close brackets and do not use superfluous whitespaces. Also you
|
|
<EM>must not</EM> use <TT>ldap_uidattr</TT> attribute in filter because this
|
|
attribute will be substituted in LDAP filter automatically.
|
|
</DL>
|
|
<!--TOC subsubsection Examples-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc44">4.5.3</A> <A NAME="ldapexamples">Examples</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:ldapexamples"></A>
|
|
<!--TOC paragraph Common example-->
|
|
|
|
<H5 CLASS="paragraph"><A NAME="ldapcommonexample">Common example</A></H5><!--SEC END -->
|
|
|
|
Let's say <TT>ldap.example.org</TT> is the name of our LDAP server. We have
|
|
users with their passwords in <TT>"ou=Users,dc=example,dc=org"</TT> directory.
|
|
Also we have addressbook, which contains users emails and their additional
|
|
infos in <TT>"ou=AddressBook,dc=example,dc=org"</TT> directory. Corresponding
|
|
authentication section should looks like this:
|
|
<PRE CLASS="verbatim">
|
|
%% authentication method
|
|
{auth_method, ldap}.
|
|
%% DNS name of our LDAP server
|
|
{ldap_servers, ["ldap.example.org"]}.
|
|
%% Bind to LDAP server as "cn=Manager,dc=example,dc=org" with password "secret"
|
|
{ldap_rootdn, "cn=Manager,dc=example,dc=org"}.
|
|
{ldap_password, "secret"}.
|
|
%% define the user's base
|
|
{ldap_base, "ou=Users,dc=example,dc=org"}.
|
|
%% We want to authorize users from 'shadowAccount' object class only
|
|
{ldap_filter, "(objectClass=shadowAccount)"}.
|
|
</PRE>
|
|
Now we want to use users LDAP-info as their vCards. We have four attributes
|
|
defined in our LDAP schema: <TT>"mail"</TT> — email address, <TT>"givenName"</TT>
|
|
— first name, <TT>"sn"</TT> — second name, <TT>"birthDay"</TT> — birthday.
|
|
Also we want users to search each other. Let's see how we can set it up:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
...
|
|
{mod_vcard_ldap,
|
|
[
|
|
%% We use the same server and port, but want to bind anonymously because
|
|
%% our LDAP server accepts anonymous requests to
|
|
%% "ou=AddressBook,dc=example,dc=org" subtree.
|
|
{ldap_rootdn, ""},
|
|
{ldap_password, ""},
|
|
%% define the addressbook's base
|
|
{ldap_base, "ou=AddressBook,dc=example,dc=org"},
|
|
%% user's part of JID is located in the "mail" attribute
|
|
{ldap_uidattr, "mail"},
|
|
%% common format for our emails
|
|
{ldap_uidattr_format, "%u@mail.example.org"},
|
|
%% We have to define empty filter here, because entries in addressbook does not
|
|
%% belong to shadowAccount object class
|
|
{ldap_filter, ""},
|
|
%% Now we want to define vCard pattern
|
|
{ldap_vcard_map,
|
|
[{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname
|
|
{"GIVEN", "%s", ["givenName"]},
|
|
{"FAMILY", "%s", ["sn"]},
|
|
{"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John"
|
|
{"EMAIL", "%s", ["mail"]},
|
|
{"BDAY", "%s", ["birthDay"]}]},
|
|
%% Search form
|
|
{ldap_search_fields,
|
|
[{"User", "%u"},
|
|
{"Name", "givenName"},
|
|
{"Family Name", "sn"},
|
|
{"Email", "mail"},
|
|
{"Birthday", "birthDay"}]},
|
|
%% vCard fields to be reported
|
|
%% Note that JID is always returned with search results
|
|
{ldap_search_reported,
|
|
[{"Full Name", "FN"},
|
|
{"Nickname", "NICKNAME"},
|
|
{"Birthday", "BDAY"}]}
|
|
]}
|
|
...
|
|
}.
|
|
</PRE>
|
|
Note that <TT>mod_vcard_ldap</TT> module checks for the existence of the user before
|
|
searching in his information in LDAP.<BR>
|
|
<BR>
|
|
<!--TOC paragraph Active Directory-->
|
|
|
|
<H5 CLASS="paragraph"><A NAME="ad">Active Directory</A></H5><!--SEC END -->
|
|
|
|
<A NAME="sec:ad"></A>
|
|
|
|
Active Directory is just an LDAP-server with predefined attributes. A sample
|
|
configuration is showed below:
|
|
<PRE CLASS="verbatim">
|
|
{auth_method, ldap}.
|
|
{ldap_servers, ["office.org"]}. % List of LDAP servers
|
|
{ldap_base, "DC=office,DC=org"}. % Search base of LDAP directory
|
|
{ldap_rootdn, "CN=Administrator,CN=Users,DC=office,DC=org"}. % LDAP manager
|
|
{ldap_password, "*******"}. % Password to LDAP manager
|
|
{ldap_uidattr, "sAMAccountName"}.
|
|
{ldap_filter, "(memberOf=*)"}.
|
|
|
|
{mod_vcard_ldap,
|
|
[{ldap_vcard_map,
|
|
[{"NICKNAME", "%u", []},
|
|
{"GIVEN", "%s", ["givenName"]},
|
|
{"MIDDLE", "%s", ["initials"]},
|
|
{"FAMILY", "%s", ["sn"]},
|
|
{"FN", "%s", ["displayName"]},
|
|
{"EMAIL", "%s", ["mail"]},
|
|
{"ORGNAME", "%s", ["company"]},
|
|
{"ORGUNIT", "%s", ["department"]},
|
|
{"CTRY", "%s", ["c"]},
|
|
{"LOCALITY", "%s", ["l"]},
|
|
{"STREET", "%s", ["streetAddress"]},
|
|
{"REGION", "%s", ["st"]},
|
|
{"PCODE", "%s", ["postalCode"]},
|
|
{"TITLE", "%s", ["title"]},
|
|
{"URL", "%s", ["wWWHomePage"]},
|
|
{"DESC", "%s", ["description"]},
|
|
{"TEL", "%s", ["telephoneNumber"]}]},
|
|
{ldap_search_fields,
|
|
[{"User", "%u"},
|
|
{"Name", "givenName"},
|
|
{"Family Name", "sn"},
|
|
{"Email", "mail"},
|
|
{"Company", "company"},
|
|
{"Department", "department"},
|
|
{"Role", "title"},
|
|
{"Description", "description"},
|
|
{"Phone", "telephoneNumber"}]},
|
|
{ldap_search_reported,
|
|
[{"Full Name", "FN"},
|
|
{"Nickname", "NICKNAME"},
|
|
{"Email", "EMAIL"}]}
|
|
]
|
|
}.
|
|
</PRE>
|
|
<!--TOC section Modules Configuration-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc45">5</A> <A NAME="modules">Modules Configuration</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:modules"></A>
|
|
|
|
The option <TT>modules</TT> defines the list of modules that will be loaded after
|
|
<TT>ejabberd</TT>'s startup. Each entry in the list is a tuple in which the first
|
|
element is the name of a module and the second is a list of options for that
|
|
module.<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
In this example only the module <TT>mod_echo</TT> is loaded and no module
|
|
options are specified between the square brackets:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[{mod_echo, []}
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">In the second example the modules <TT>mod_echo</TT>, <TT>mod_time</TT>, and
|
|
<TT>mod_version</TT> are loaded without options. Remark that, besides the last entry,
|
|
all entries end with a comma:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[{mod_echo, []},
|
|
{mod_time, []},
|
|
{mod_version, []}
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection Overview-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc46">5.1</A> <A NAME="modoverview">Overview</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modoverview"></A>
|
|
|
|
The following table lists all modules available in the official <TT>ejabberd</TT>
|
|
distribution. You can find more
|
|
<A HREF="http://ejabberd.jabber.ru/contributions">contributed modules</A> on the
|
|
<TT>ejabberd</TT> website. Please remember that these contributions might not work or
|
|
that they can contain severe bugs and security leaks. Therefore, use them at
|
|
your own risk!<BR>
|
|
<BR>
|
|
You can see which database backend each module needs by looking at the suffix:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
`_ldap', this means that the module needs an LDAP server as backend.
|
|
<LI CLASS="li-itemize">`_odbc', this means that the module needs a supported database
|
|
(see <A HREF="#sec:database">4</A>) as backend.
|
|
<LI CLASS="li-itemize">No suffix, this means that the modules uses Erlang's built-in database
|
|
Mnesia as backend.
|
|
</UL>
|
|
If you want to
|
|
It is possible to use a relational database to store pieces of
|
|
information. You can do this by changing the module name to a name with an
|
|
<TT>_odbc</TT> suffix in <TT>ejabberd</TT> config file. You can use a relational
|
|
database for the following data:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Last connection date and time: Use <TT>mod_last_odbc</TT> instead of
|
|
<TT>mod_last</TT>.
|
|
<LI CLASS="li-itemize">Offline messages: Use <TT>mod_offline_odbc</TT> instead of
|
|
<TT>mod_offline</TT>.
|
|
<LI CLASS="li-itemize">Rosters: Use <TT>mod_roster_odbc</TT> instead of <TT>mod_roster</TT>.
|
|
<LI CLASS="li-itemize">Users' VCARD: Use <TT>mod_vcard_odbc</TT> instead of <TT>mod_vcard</TT>.
|
|
</UL>
|
|
<BLOCKQUOTE CLASS="table"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
<TABLE BORDER=1 CELLSPACING=0 CELLPADDING=1>
|
|
<TR><TD ALIGN=left NOWRAP>Module</TD>
|
|
<TD ALIGN=left NOWRAP>Feature</TD>
|
|
<TD ALIGN=left NOWRAP>Dependencies</TD>
|
|
<TD ALIGN=left NOWRAP>Needed for XMPP?</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_adhoc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Ad-Hoc Commands (<A HREF="http://www.jabber.org/jeps/jep-0050.html">JEP-0050</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_announce</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Manage announcements</TD>
|
|
<TD ALIGN=left NOWRAP><TT>mod_adhoc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_configure</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Support for online</TD>
|
|
<TD ALIGN=left NOWRAP><TT>mod_adhoc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>configuration of <TT>ejabberd</TT></TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_disco</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Service Discovery (<A HREF="http://www.jabber.org/jeps/jep-0030.html">JEP-0030</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_echo</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Echoes Jabber packets</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_irc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>IRC transport</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_last</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Last Activity (<A HREF="http://www.jabber.org/jeps/jep-0012.html">JEP-0012</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_last_odbc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Last Activity (<A HREF="http://www.jabber.org/jeps/jep-0012.html">JEP-0012</A>)</TD>
|
|
<TD ALIGN=left NOWRAP>supported database (*)</TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_muc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Multi-User Chat (<A HREF="http://www.jabber.org/jeps/jep-0045.html">JEP-0045</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_muc_log</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Multi-User Chat room logging</TD>
|
|
<TD ALIGN=left NOWRAP><TT>mod_muc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_offline</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Offline message storage</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_offline_odbc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Offline message storage</TD>
|
|
<TD ALIGN=left NOWRAP>supported database (*)</TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_privacy</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Blocking Communication</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>Yes</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_private</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Private XML Storage (<A HREF="http://www.jabber.org/jeps/jep-0049.html">JEP-0049</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_pubsub</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Publish-Subscribe (<A HREF="http://www.jabber.org/jeps/jep-0060.html">JEP-0060</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_register</TT></TD>
|
|
<TD ALIGN=left NOWRAP>In-Band Registration (<A HREF="http://www.jabber.org/jeps/jep-0077.html">JEP-0077</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_roster</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Roster management</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>Yes (**)</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_roster_odbc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Roster management</TD>
|
|
<TD ALIGN=left NOWRAP>supported database (*)</TD>
|
|
<TD ALIGN=left NOWRAP>Yes (**)</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_service_log</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Copy user messages to logger service</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_shared_roster</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Shared roster management</TD>
|
|
<TD ALIGN=left NOWRAP><TT>mod_roster</TT> or</TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP><TT>mod_roster_odbc</TT></TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_stats</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Statistics Gathering (<A HREF="http://www.jabber.org/jeps/jep-0039.html">JEP-0039</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_time</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Entity Time (<A HREF="http://www.jabber.org/jeps/jep-0090.html">JEP-0090</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_vcard</TT></TD>
|
|
<TD ALIGN=left NOWRAP>vcard-temp (<A HREF="http://www.jabber.org/jeps/jep-0054.html">JEP-0054</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_vcard_ldap</TT></TD>
|
|
<TD ALIGN=left NOWRAP>vcard-temp (<A HREF="http://www.jabber.org/jeps/jep-0054.html">JEP-0054</A>)</TD>
|
|
<TD ALIGN=left NOWRAP>LDAP server</TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_vcard_odbc</TT></TD>
|
|
<TD ALIGN=left NOWRAP>vcard-temp (<A HREF="http://www.jabber.org/jeps/jep-0054.html">JEP-0054</A>)</TD>
|
|
<TD ALIGN=left NOWRAP>supported database (*)</TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>mod_version</TT></TD>
|
|
<TD ALIGN=left NOWRAP>Software Version (<A HREF="http://www.jabber.org/jeps/jep-0092.html">JEP-0092</A>)</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
<TD ALIGN=left NOWRAP>No</TD>
|
|
</TR></TABLE>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
(*) For a list of supported databases, see section <A HREF="#sec:database">4</A>.
|
|
<LI CLASS="li-itemize">(**) This module or a similar one with another database backend is needed for
|
|
XMPP compliancy.
|
|
</UL>
|
|
<!--TOC subsection Common Options-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc47">5.2</A> <A NAME="modcommonoptions">Common Options</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modcommonoptions"></A>
|
|
The following options are used by many modules. Therefore, they are described in
|
|
this separate section.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection <TT>iqdisc</TT>-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc48">5.2.1</A> <A NAME="modiqdiscoption"><TT>iqdisc</TT></A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:modiqdiscoption"></A>
|
|
|
|
Many modules define handlers for processing IQ queries of different namespaces
|
|
to this server or to a user (e. g. to <TT>example.org</TT> or to
|
|
<TT>user@example.org</TT>). This option defines processing discipline for
|
|
these queries. Possible values are:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>no_queue</TT></B><DD CLASS="dd-description"> All queries of a namespace with this processing discipline are
|
|
processed immediately. This also means that no other packets can be processed
|
|
until this one has been completely processed. Hence this discipline is not
|
|
recommended if the processing of a query can take a relatively long time.
|
|
<DT CLASS="dt-description"><B><TT>one_queue</TT></B><DD CLASS="dd-description"> In this case a separate queue is created for the processing
|
|
of IQ queries of a namespace with this discipline. In addition, the processing
|
|
of this queue is done in parallel with that of other packets. This discipline
|
|
is most recommended.
|
|
<DT CLASS="dt-description"><B><TT>parallel</TT></B><DD CLASS="dd-description"> For every packet with this discipline a separate Erlang process
|
|
is spawned. Consequently, all these packets are processed in parallel.
|
|
Although spawning of Erlang process has a relatively low cost, this can break
|
|
the server's normal work, because the Erlang emulator has a limit on the
|
|
number of processes (32000 by default).
|
|
</DL>
|
|
Example:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_time, [{iqdisc, no_queue}]},
|
|
...
|
|
]}.
|
|
</PRE>
|
|
<!--TOC subsubsection <TT>hosts</TT>-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc49">5.2.2</A> <A NAME="modhostsoption"><TT>hosts</TT></A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:modhostsoption"></A>
|
|
|
|
A module acting as a service can have one or more hostnames. These hostnames
|
|
can be defined with the <TT>hosts</TT> option.<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Serving the echo module on one domain:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_echo, [{hosts, ["echo.example.org"]}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">Backwards compatibility with older <TT>ejabberd</TT> versions can be retained
|
|
with:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_echo, [{host, "echo.example.org"}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<LI CLASS="li-itemize">Serving the echo module on two domains:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_echo, [{hosts, ["echo.example.net", "echo.example.com"]}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_announce</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc50">5.3</A> <A NAME="modannounce"><TT>mod_announce</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modannounce"></A>
|
|
|
|
This module enables configured users to broadcast announcements and to set
|
|
the message of the day (MOTD). Configured users can do these actions with their
|
|
Jabber client by sending messages to specific JIDs. These JIDs are listed in
|
|
next paragraph. The first JID in each entry will apply only to the virtual host
|
|
<TT>example.org</TT>, while the JID between brackets will apply to all virtual
|
|
hosts:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>example.org/announce/all (example.org/announce/all-hosts/all)</TT></B><DD CLASS="dd-description"> The
|
|
message is sent to all registered users. If the user is online and connected
|
|
to several resources, only the resource with the highest priority will receive
|
|
the message. If the registered user is not connected, the message will be
|
|
stored offline in assumption that offline storage
|
|
(see section <A HREF="#sec:modoffline">5.10</A>) is enabled.
|
|
<DT CLASS="dt-description"><B><TT>example.org/announce/online (example.org/announce/all-hosts/online)</TT></B><DD CLASS="dd-description">The
|
|
message is sent to all connected users. If the user is online and connected
|
|
to several resources, all resources will receive the message.
|
|
<DT CLASS="dt-description"><B><TT>example.org/announce/motd (example.org/announce/all-hosts/motd)</TT></B><DD CLASS="dd-description">The
|
|
message is set as the message of the day (MOTD) and is sent to users when they
|
|
login. In addition the message is sent to all connected users (similar to
|
|
<TT>announce/online</TT>).
|
|
<DT CLASS="dt-description"><B><TT>example.org/announce/motd/update (example.org/announce/all-hosts/motd/update)</TT></B><DD CLASS="dd-description">
|
|
The message is set as message of the day (MOTD) and is sent to users when they
|
|
login. The message is <EM>not sent</EM> to any currently connected user.
|
|
<DT CLASS="dt-description"><B><TT>example.org/announce/motd/delete (example.org/announce/all-hosts/motd/delete)</TT></B><DD CLASS="dd-description">
|
|
Any message sent to this JID removes the existing message of the day (MOTD).
|
|
</DL>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>access</TT></B><DD CLASS="dd-description"> This option specifies who is allowed to
|
|
send announcements and to set the message of the day (by default, nobody is
|
|
able to send such messages).
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Only administrators can send announcements:
|
|
<PRE CLASS="verbatim">
|
|
{access, announce, [{allow, admins}]}.
|
|
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_announce, [{access, announce}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">Administrators as well as the direction can send announcements:
|
|
<PRE CLASS="verbatim">
|
|
{acl, direction, {user, "big_boss", "example.org"}}.
|
|
{acl, direction, {user, "assistant", "example.org"}}.
|
|
{acl, admins, {user, "admin", "example.org"}}.
|
|
...
|
|
{access, announce, [{allow, admins},
|
|
{allow, direction}]}.
|
|
...
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_announce, [{access, announce}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_disco</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc51">5.4</A> <A NAME="moddisco"><TT>mod_disco</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:moddisco"></A>
|
|
|
|
This module adds support for Service Discovery (<A HREF="http://www.jabber.org/jeps/jep-0030.html">JEP-0030</A>). With
|
|
this module enabled, services on your server can be discovered by
|
|
Jabber clients. Note that <TT>ejabberd</TT> has no modules with support
|
|
for the superseded Jabber Browsing (<A HREF="http://www.jabber.org/jeps/jep-0011.html">JEP-0011</A>) and Agent Information
|
|
(<A HREF="http://www.jabber.org/jeps/jep-0094.html">JEP-0094</A>). Accordingly, Jabber clients need to have support for
|
|
the newer Service Discovery protocol if you want them be able to discover
|
|
the services you offer.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Service Discovery (<TT>http://jabber.org/protocol/disco#items</TT> and
|
|
<TT>http://jabber.org/protocol/disco#info</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
<DT CLASS="dt-description"><B><TT>extra_domains</TT></B><DD CLASS="dd-description"> With this option,
|
|
extra domains can be added to the Service Discovery item list.
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
To serve a link to the Jabber User Directory on <TT>jabber.org</TT>:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_disco, [{extra_domains, ["users.jabber.org"]}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">To serve a link to the transports on another server:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_disco, [{extra_domains, ["icq.example.com",
|
|
"msn.example.com"]}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">To serve a link to a few friendly servers:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_disco, [{extra_domains, ["example.org",
|
|
"example.com"]}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_echo</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc52">5.5</A> <A NAME="modecho"><TT>mod_echo</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modecho"></A>
|
|
|
|
This module simply echoes any Jabber
|
|
packet back to the sender. This mirror can be of interest for
|
|
<TT>ejabberd</TT> and Jabber client debugging.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
|
|
<B><TT>hosts</TT></B><DD CLASS="dd-description"> This option defines the hostnames of the
|
|
service (see section <A HREF="#sec:modhostsoption">5.2.2</A>). If neither <TT>hosts</TT> nor
|
|
the old <TT>host</TT> is present, the prefix `<TT>echo.</TT>' is added to all
|
|
<TT>ejabberd</TT> hostnames.
|
|
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Mirror, mirror, on the wall, who is the most beautiful
|
|
of them all?
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_echo, [{hosts, ["mirror.example.org"]}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">If you still do not understand the inner workings of <TT>mod_echo</TT>,
|
|
you can find a few more examples in section <A HREF="#sec:modhostsoption">5.2.2</A>.
|
|
</UL>
|
|
<!--TOC subsection <TT>mod_irc</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc53">5.6</A> <A NAME="modirc"><TT>mod_irc</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modirc"></A>
|
|
|
|
This module is an IRC transport that can be used to join channels on IRC
|
|
servers.<BR>
|
|
<BR>
|
|
End user information:
|
|
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
A Jabber client with `groupchat 1.0' support or Multi-User
|
|
Chat support (<A HREF="http://www.jabber.org/jeps/jep-0045.html">JEP-0045</A>) is necessary to join IRC channels.
|
|
<LI CLASS="li-itemize">An IRC channel can be joined in nearly the same way as joining a
|
|
Jabber Multi-User Chat room. The difference is that the room name will
|
|
be `channel%<TT>irc.example.org</TT>' in case <TT>irc.example.org</TT> is
|
|
the IRC server hosting `channel'. And of course the host should point
|
|
to the IRC transport instead of the Multi-User Chat service.
|
|
<LI CLASS="li-itemize">You can register your nickame by sending `IDENTIFY password' to<BR>
|
|
<TT>nickserver!irc.example.org@irc.jabberserver.org</TT>.
|
|
<LI CLASS="li-itemize">Entering your password is possible by sending `LOGIN nick password'<BR>
|
|
to <TT>nickserver!irc.example.org@irc.jabberserver.org</TT>.
|
|
<LI CLASS="li-itemize">When using a popular Jabber server, it can occur that no
|
|
connection can be achieved with some IRC servers because they limit the
|
|
number of conections from one IP.
|
|
</UL>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
|
|
<B><TT>hosts</TT></B><DD CLASS="dd-description"> This option defines the hostnames of the
|
|
service (see section <A HREF="#sec:modhostsoption">5.2.2</A>). If neither <TT>hosts</TT> nor
|
|
the old <TT>host</TT> is present, the prefix `<TT>irc.</TT>' is added to all
|
|
<TT>ejabberd</TT> hostnames.
|
|
|
|
<DT CLASS="dt-description"><B><TT>access</TT></B><DD CLASS="dd-description"> This option can be used to specify who
|
|
may use the IRC transport (default value: <TT>all</TT>).
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
In the first example, the IRC transport is available on (all) your
|
|
virtual host(s) with the prefix `<TT>irc.</TT>'. Furthermore, anyone is
|
|
able to use the transport.
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_irc, [{access, all}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">In next example the IRC transport is available on the two virtual hosts
|
|
<TT>example.net</TT> and <TT>example.com</TT> with different prefixes on each host.
|
|
Moreover, the transport is only accessible by paying customers registered on
|
|
our domains and on other servers.
|
|
<PRE CLASS="verbatim">
|
|
{acl, paying_customers, {user, "customer1", "example.net"}}.
|
|
{acl, paying_customers, {user, "customer2", "example.com"}}.
|
|
{acl, paying_customers, {user, "customer3", "example.org"}}.
|
|
...
|
|
{access, paying_customers, [{allow, paying_customers},
|
|
{deny, all}]}.
|
|
...
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_irc, [{access, paying_customers},
|
|
{hosts, ["irc.example.net", "irc-transport.example.com"]}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_last</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc54">5.7</A> <A NAME="modlast"><TT>mod_last</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modlast"></A>
|
|
|
|
This module adds support for Last Activity (<A HREF="http://www.jabber.org/jeps/jep-0012.html">JEP-0012</A>). It can be used to
|
|
discover when a disconnected user last accessed the server, to know when a
|
|
connected user was last active on the server, or to query the uptime of the
|
|
<TT>ejabberd</TT> server.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Last activity (<TT>jabber:iq:last</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
<!--TOC subsection <TT>mod_muc</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc55">5.8</A> <A NAME="modmuc"><TT>mod_muc</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modmuc"></A>
|
|
|
|
With this module enabled, your server will support Multi-User Chat
|
|
(<A HREF="http://www.jabber.org/jeps/jep-0045.html">JEP-0045</A>). End users will be able to join text conferences. Notice
|
|
that this module is not (yet) clusterable.<BR>
|
|
<BR>
|
|
Some of the features of Multi-User Chat:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Sending private messages to room participants.
|
|
<LI CLASS="li-itemize">Inviting users.
|
|
<LI CLASS="li-itemize">Setting a conference topic.
|
|
<LI CLASS="li-itemize">Creating password protected rooms.
|
|
<LI CLASS="li-itemize">Kicking and banning participants.
|
|
</UL>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
|
|
<B><TT>hosts</TT></B><DD CLASS="dd-description"> This option defines the hostnames of the
|
|
service (see section <A HREF="#sec:modhostsoption">5.2.2</A>). If neither <TT>hosts</TT> nor
|
|
the old <TT>host</TT> is present, the prefix `<TT>conference.</TT>' is added to all
|
|
<TT>ejabberd</TT> hostnames.
|
|
|
|
<DT CLASS="dt-description"><B><TT>access</TT></B><DD CLASS="dd-description"> You can specify who is allowed to use
|
|
the Multi-User Chat service (by default, everyone is allowed to use it).
|
|
<DT CLASS="dt-description"><B><TT>access_create</TT></B><DD CLASS="dd-description"> To configure who is
|
|
allowed to create new rooms at the Multi-User Chat service, this option
|
|
can be used (by default, everybody is allowed to create rooms).
|
|
<DT CLASS="dt-description"><B><TT>access_admin</TT></B><DD CLASS="dd-description"> This option specifies
|
|
who is allowed to administrate the Multi-User Chat service (the default
|
|
value is <TT>none</TT>, which means that only the room creator can
|
|
administer his room). By sending a message to the service JID,
|
|
administrators can send service messages that will be displayed in every
|
|
active room.
|
|
<DT CLASS="dt-description"><B><TT>history_size</TT></B><DD CLASS="dd-description"> A small history of the
|
|
current discussion is sent to users when they enter the room. With this option
|
|
you can define the number of history messages to keep and send to users
|
|
joining the room. The value is an integer. Setting the value to <TT>0</TT>
|
|
disables the history feature and, as a result, nothing is kept in memory. The
|
|
default value is <TT>20</TT>. This value is global and thus affects all rooms on
|
|
the server.
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
In the first example everyone is allowed to use the Multi-User Chat
|
|
service. Everyone will also be able to create new rooms but only the user
|
|
<TT>admin@example.org</TT> is allowed to administrate any room. In this
|
|
example he is also a global administrator. When <TT>admin@example.org</TT>
|
|
sends a message such as `Tomorrow, the Jabber server will be moved
|
|
to new hardware. This will involve service breakdowns around 23:00 UMT.
|
|
We apologise for this inconvenience.' to <TT>conference.example.org</TT>,
|
|
it will be displayed in all active rooms. In this example the history
|
|
feature is disabled.
|
|
<PRE CLASS="verbatim">
|
|
{acl, admins, {user, "admin", "example.org"}}.
|
|
...
|
|
{access, muc_admins, [{allow, admins}]}.
|
|
...
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_muc, [{access, all},
|
|
{access_create, all},
|
|
{access_admin, muc_admins},
|
|
{history_size, 0}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">In the second example the Multi-User Chat service is only accessible by
|
|
paying customers registered on our domains and on other servers. Of course
|
|
the administrator is also allowed to access rooms. In addition, he is the
|
|
only authority able to create and administer rooms. When
|
|
<TT>admin@example.org</TT> sends a message such as `Tomorrow, the Jabber
|
|
server will be moved to new hardware. This will involve service breakdowns
|
|
around 23:00 UMT. We apologise for this inconvenience.' to
|
|
<TT>conference.example.org</TT>, it will be displayed in all active rooms. No
|
|
<TT>history_size</TT> option is used, this means that the feature is enabled
|
|
and the default value of 20 history messages will be send to the users.
|
|
<PRE CLASS="verbatim">
|
|
{acl, paying_customers, {user, "customer1", "example.net"}}.
|
|
{acl, paying_customers, {user, "customer2", "example.com"}}.
|
|
{acl, paying_customers, {user, "customer3", "example.org"}}.
|
|
{acl, admins, {user, "admin", "example.org"}}.
|
|
...
|
|
{access, muc_admins, [{allow, admins},
|
|
{deny, all}]}.
|
|
{access, muc_access, [{allow, paying_customers},
|
|
{allow, admins},
|
|
{deny, all}]}.
|
|
...
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_muc, [{access, muc_access},
|
|
{access_create, muc_admins},
|
|
{access_admin, muc_admins}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_muc_log</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc56">5.9</A> <A NAME="modmuclog"><TT>mod_muc_log</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modmuclog"></A>
|
|
|
|
This module enables optional logging of Multi-User Chat (MUC) conversations to
|
|
HTML. Once you enable this module, users can join a chatroom using a MUC capable
|
|
Jabber client, and if they have enough privileges, they can request the
|
|
configuration form in which they can set the option to enable chatroom logging.<BR>
|
|
<BR>
|
|
Features:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Chatroom details are added on top of each page: room title, JID,
|
|
author, subject and configuration.
|
|
<LI CLASS="li-itemize">
|
|
Room title and JID are links to join the chatroom (using
|
|
<A HREF="http://www.ietf.org/rfc/rfc4622.txt">XMPP URIs</A>).
|
|
<LI CLASS="li-itemize">Subject and chatroom configuration changes are tracked and displayed.
|
|
<LI CLASS="li-itemize">Joins, leaves, nick changes, kicks, bans and `/me' are tracked and
|
|
displayed, including the reason if available.
|
|
<LI CLASS="li-itemize">Generated HTML files are XHTML 1.0 Transitional and CSS compliant.
|
|
<LI CLASS="li-itemize">Timestamps are self-referencing links.
|
|
<LI CLASS="li-itemize">Links on top for quicker navigation: Previous day, Next day, Up.
|
|
<LI CLASS="li-itemize">CSS is used for style definition, and a custom CSS file can be used.
|
|
<LI CLASS="li-itemize">URLs on messages and subjects are converted to hyperlinks.
|
|
<LI CLASS="li-itemize">Timezone used on timestamps is shown on the log files.
|
|
<LI CLASS="li-itemize">A custom link can be added on top of each page.
|
|
</UL>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>access_log</TT></B><DD CLASS="dd-description">
|
|
This option restricts which users are allowed to enable or disable chatroom
|
|
logging. The default value is <TT>muc_admin</TT>. Note for this default setting
|
|
you need to have an access rule for <TT>muc_admin</TT> in order to take effect.
|
|
<DT CLASS="dt-description"><B><TT>cssfile</TT></B><DD CLASS="dd-description">
|
|
With this option you can set whether the HTML files should have a custom CSS
|
|
file or if they need to use the embedded CSS file. Allowed values are
|
|
<TT>false</TT> and an URL to a CSS file. With the first value, HTML files will
|
|
include the embedded CSS code. With the latter, you can specify the URL of the
|
|
custom CSS file (for example: `http://example.com/my.css'). The default value
|
|
is <TT>false</TT>.
|
|
<DT CLASS="dt-description"><B><TT>dirtype</TT></B><DD CLASS="dd-description">
|
|
The type of the created directories can be specified with this option. Allowed
|
|
values are <TT>subdirs</TT> and <TT>plain</TT>. With the first value,
|
|
subdirectories are created for each year and month. With the latter, the
|
|
names of the log files contain the full date, and there are no subdirectories.
|
|
The default value is <TT>subdirs</TT>.
|
|
<DT CLASS="dt-description"><B><TT>outdir</TT></B><DD CLASS="dd-description">
|
|
This option sets the full path to the directory in which the HTML files should
|
|
be stored. Make sure the <TT>ejabberd</TT> daemon user has write access on that
|
|
directory. The default value is <TT>"www/muc"</TT>.
|
|
<DT CLASS="dt-description"><B><TT>timezone</TT></B><DD CLASS="dd-description">
|
|
The time zone for the logs is configurable with this option. Allowed values
|
|
are <TT>local</TT> and <TT>universal</TT>. With the first value, the local time,
|
|
as reported to Erlang by the operating system, will be used. With the latter,
|
|
GMT/UTC time will be used. The default value is <TT>local</TT>.
|
|
<DT CLASS="dt-description"><B><TT>top_link</TT></B><DD CLASS="dd-description">
|
|
With this option you can customize the link on the top right corner of each
|
|
log file. The syntax of this option is <TT>{"URL", "Text"}</TT>. The default
|
|
value is <TT>{"/", "Home"}</TT>.
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
In the first example any chatroom owner can enable logging, and a
|
|
custom CSS file will be used (http://example.com/my.css). Further, the names
|
|
of the log files will contain the full date, and there will be no
|
|
subdirectories. The log files will be stored in /var/www/muclogs, and the
|
|
time zone will be GMT/UTC. Finally, the top link will be
|
|
<CODE><a href="http://www.jabber.ru">Jabber.ru</a></CODE>.
|
|
<PRE CLASS="verbatim">
|
|
{access, muc, [{allow, all}]}.
|
|
...
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_muc_log, [
|
|
{access_log, muc},
|
|
{cssfile, "http://example.com/my.css"},
|
|
{dirtype, plain},
|
|
{outdir, "/var/www/muclogs"},
|
|
{timezone, universal},
|
|
{top_link, {"http://www.jabber.ru", "Jabber.ru"}}
|
|
]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">In the second example only <TT>admin1@example.org</TT> and
|
|
<TT>admin2@example.net</TT> can enable logging, and the embedded CSS file will be
|
|
used. Further, the names of the log files will only contain the day (number),
|
|
and there will be subdirectories for each year and month. The log files will
|
|
be stored in /var/www/muclogs, and the local time will be used. Finally, the
|
|
top link will be the default <CODE><a href="/">Home</a></CODE>.
|
|
<PRE CLASS="verbatim">
|
|
{acl, admins, {user, "admin1", "example.org"}}.
|
|
{acl, admins, {user, "admin2", "example.net"}}.
|
|
...
|
|
{access, muc_log, [{allow, admins},
|
|
{deny, all}]}.
|
|
...
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_muc_log, [
|
|
{access_log, muc_log},
|
|
{cssfile, false},
|
|
{dirtype, subdirs},
|
|
{outdir, "/var/www/muclogs"},
|
|
{timezone, local}
|
|
]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_offline</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc57">5.10</A> <A NAME="modoffline"><TT>mod_offline</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modoffline"></A>
|
|
|
|
This module implements offline message storage. This means that all messages
|
|
sent to an offline user will be stored on the server until that user comes
|
|
online again. Thus it is very similar to how email works. Note that
|
|
<TT>ejabberdctl</TT> has a command to delete expired messages
|
|
(see section <A HREF="#sec:ejabberdctl">7.2</A>).<BR>
|
|
<BR>
|
|
<!--TOC subsection <TT>mod_privacy</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc58">5.11</A> <A NAME="modprivacy"><TT>mod_privacy</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modprivacy"></A>
|
|
|
|
This module implements Blocking Communication (also known as Privacy Rules)
|
|
as defined in section 10 from XMPP IM. If end users have support for it in
|
|
their Jabber client, they will be able to:
|
|
<BLOCKQUOTE CLASS="quote">
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Retrieving one's privacy lists.
|
|
<LI CLASS="li-itemize">Adding, removing, and editing one's privacy lists.
|
|
<LI CLASS="li-itemize">Setting, changing, or declining active lists.
|
|
<LI CLASS="li-itemize">Setting, changing, or declining the default list (i.e., the list that
|
|
is active by default).
|
|
<LI CLASS="li-itemize">Allowing or blocking messages based on JID, group, or subscription type
|
|
(or globally).
|
|
<LI CLASS="li-itemize">Allowing or blocking inbound presence notifications based on JID, group,
|
|
or subscription type (or globally).
|
|
<LI CLASS="li-itemize">Allowing or blocking outbound presence notifications based on JID, group,
|
|
or subscription type (or globally).
|
|
<LI CLASS="li-itemize">Allowing or blocking IQ stanzas based on JID, group, or subscription type
|
|
(or globally).
|
|
<LI CLASS="li-itemize">Allowing or blocking all communications based on JID, group, or
|
|
subscription type (or globally).
|
|
</UL>
|
|
(from <A HREF="http://www.xmpp.org/specs/rfc3921.html#privacy"><TT>http://www.xmpp.org/specs/rfc3921.html#privacy</TT></A>)
|
|
</BLOCKQUOTE>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Blocking Communication (<TT>jabber:iq:privacy</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
<!--TOC subsection <TT>mod_private</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc59">5.12</A> <A NAME="modprivate"><TT>mod_private</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modprivate"></A>
|
|
|
|
This module adds support for Private XML Storage (<A HREF="http://www.jabber.org/jeps/jep-0049.html">JEP-0049</A>):
|
|
<BLOCKQUOTE CLASS="quote">
|
|
Using this method, Jabber entities can store private data on the server and
|
|
retrieve it whenever necessary. The data stored might be anything, as long as
|
|
it is valid XML. One typical usage for this namespace is the server-side storage
|
|
of client-specific preferences; another is Bookmark Storage (<A HREF="http://www.jabber.org/jeps/jep-0048.html">JEP-0048</A>).
|
|
</BLOCKQUOTE>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Private XML Storage (<TT>jabber:iq:private</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
<!--TOC subsection <TT>mod_pubsub</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc60">5.13</A> <A NAME="modpubsub"><TT>mod_pubsub</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modpubsub"></A>
|
|
|
|
This module offers a Publish-Subscribe Service (<A HREF="http://www.jabber.org/jeps/jep-0060.html">JEP-0060</A>).
|
|
Publish-Subscribe can be used to develop (examples are taken from the JEP):
|
|
<BLOCKQUOTE CLASS="quote">
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
news feeds and content syndacation,
|
|
<LI CLASS="li-itemize">avatar management,
|
|
<LI CLASS="li-itemize">shared bookmarks,
|
|
<LI CLASS="li-itemize">auction and trading systems,
|
|
<LI CLASS="li-itemize">online catalogs,
|
|
<LI CLASS="li-itemize">workflow systems,
|
|
<LI CLASS="li-itemize">network management systems,
|
|
<LI CLASS="li-itemize">NNTP gateways,
|
|
<LI CLASS="li-itemize">vCard/profile management,
|
|
<LI CLASS="li-itemize">and weblogs.
|
|
</UL>
|
|
</BLOCKQUOTE>
|
|
|
|
Another example is <A HREF="http://www.process-one.net/en/projects/j-eai/">J-EAI</A>.
|
|
This is an XMPP-based Enterprise Application Integration (EAI) platform (also
|
|
known as ESB, the Enterprise Service Bus). The J-EAI project builts upon
|
|
<TT>ejabberd</TT>'s codebase and has contributed several features to <TT>mod_pubsub</TT>.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
|
|
<B><TT>hosts</TT></B><DD CLASS="dd-description"> This option defines the hostnames of the
|
|
service (see section <A HREF="#sec:modhostsoption">5.2.2</A>). If neither <TT>hosts</TT> nor
|
|
the old <TT>host</TT> is present, the prefix `<TT>pubsub.</TT>' is added to all
|
|
<TT>ejabberd</TT> hostnames.
|
|
|
|
<DT CLASS="dt-description"><B><TT>served_hosts</TT></B><DD CLASS="dd-description"> To specify which hosts needs to
|
|
be served, you can use this option. If absent, only the main <TT>ejabberd</TT>
|
|
host is served. <DT CLASS="dt-description"><B><TT>access_createnode</TT></B><DD CLASS="dd-description">
|
|
This option restricts which users are allowed to create pubsub nodes using
|
|
ACL and ACCESS. The default value is <TT>pubsub_createnode</TT>. </DL>
|
|
Example:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_pubsub, [{served_hosts, ["example.com",
|
|
"example.org"]},
|
|
{access_createnode, pubsub_createnode}]}
|
|
...
|
|
]}.
|
|
</PRE>
|
|
<!--TOC subsection <TT>mod_register</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc61">5.14</A> <A NAME="modregister"><TT>mod_register</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modregister"></A>
|
|
|
|
This module adds support for In-Band Registration (<A HREF="http://www.jabber.org/jeps/jep-0077.html">JEP-0077</A>). This protocol
|
|
enables end users to use a Jabber client to:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Register a new account on the server.
|
|
<LI CLASS="li-itemize">Change the password from an existing account on the server.
|
|
<LI CLASS="li-itemize">Delete an existing account on the server.
|
|
</UL>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>access</TT></B><DD CLASS="dd-description"> This option can be configured to specify
|
|
rules to restrict registration. If a rule returns `deny' on the requested
|
|
user name, registration for that user name is dennied. (there are no
|
|
restrictions by default).
|
|
<DT CLASS="dt-description"><B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for In-Band Registration (<TT>jabber:iq:register</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Next example prohibits the registration of too short account names:
|
|
<PRE CLASS="verbatim">
|
|
{acl, shortname, {user_glob, "?"}}.
|
|
{acl, shortname, {user_glob, "??"}}.
|
|
% The same using regexp:
|
|
%{acl, shortname, {user_regexp, "^..?$"}}.
|
|
...
|
|
{access, register, [{deny, shortname},
|
|
{allow, all}]}.
|
|
...
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_register, [{access, register}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">The in-band registration of new accounts can be prohibited by changing the
|
|
<TT>access</TT> option. If you really want to disable all In-Band Registration
|
|
functionality, that is changing passwords in-band and deleting accounts
|
|
in-band, you have to remove <TT>mod_register</TT> from the modules list. In this
|
|
example all In-Band Registration functionality is disabled:
|
|
<PRE CLASS="verbatim">
|
|
{access, register, [{deny, all}]}.
|
|
|
|
{modules,
|
|
[
|
|
...
|
|
% {mod_register, [{access, register}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_roster</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc62">5.15</A> <A NAME="modroster"><TT>mod_roster</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modroster"></A>
|
|
|
|
This module implements roster management as defined in <A HREF="http://www.xmpp.org/specs/rfc3921.html#roster">RFC 3921: XMPP IM</A>.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Roster Management (<TT>jabber:iq:roster</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
<!--TOC subsection <TT>mod_service_log</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc63">5.16</A> <A NAME="modservicelog"><TT>mod_service_log</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modservicelog"></A>
|
|
|
|
This module adds support for logging end user packets via a Jabber message
|
|
auditing service such as
|
|
<A HREF="http://www.funkypenguin.co.za/bandersnatch/">Bandersnatch</A>. All user
|
|
packets are encapsulated in a <CODE><route/></CODE> element and sent to the specified
|
|
service(s).<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>loggers</TT></B><DD CLASS="dd-description"> With this option a (list of) service(s)
|
|
that will receive the packets can be specified.
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
To log all end user packets to the Bandersnatch service running on
|
|
<TT>bandersnatch.example.com</TT>:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_service_log, [{loggers, ["bandersnatch.example.com"]}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">To log all end user packets to the Bandersnatch service running on
|
|
<TT>bandersnatch.example.com</TT> and the backup service on
|
|
<TT>bandersnatch.example.org</TT>:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_service_log, [{loggers, ["bandersnatch.example.com",
|
|
"bandersnatch.example.org"]}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_shared_roster</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc64">5.17</A> <A NAME="modsharedroster"><TT>mod_shared_roster</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modsharedroster"></A>
|
|
|
|
This module enables you to create shared roster groups. This means that you can
|
|
create groups of people that can see members from (other) groups in their
|
|
rosters. The big advantages of this feature are that end users do not need to
|
|
manually add all users to their rosters, and that they cannot permanently delete
|
|
users from the shared roster groups.<BR>
|
|
<BR>
|
|
Shared roster groups can be edited <EM>only</EM> via the web interface. Each group
|
|
has a unique identification and the following parameters:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B>Name</B><DD CLASS="dd-description"> The name of the group, which will be displayed in the roster.
|
|
<DT CLASS="dt-description"><B>Description</B><DD CLASS="dd-description"> The description of the group. This parameter does not affect
|
|
anything.
|
|
<DT CLASS="dt-description"><B>Members</B><DD CLASS="dd-description"> A list of full JIDs of group members, entered one per line in
|
|
the web interface.
|
|
<DT CLASS="dt-description"><B>Displayed groups</B><DD CLASS="dd-description"> A list of groups that will be in the rosters of this
|
|
group's members.
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Take the case of a computer club that wants all its members seeing each
|
|
other in their rosters. To achieve this, they need to create a shared roster
|
|
group similar to next table:
|
|
<BLOCKQUOTE CLASS="table"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
<TABLE BORDER=1 CELLSPACING=0 CELLPADDING=1>
|
|
<TR><TD ALIGN=left NOWRAP>Identification</TD>
|
|
<TD ALIGN=left NOWRAP>Group `<TT>club_members</TT>'</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Name</TD>
|
|
<TD ALIGN=left NOWRAP>Club Members</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Description</TD>
|
|
<TD ALIGN=left NOWRAP>Members from the computer club</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Members</TD>
|
|
<TD ALIGN=left NOWRAP><TABLE CELLSPACING=2 CELLPADDING=0>
|
|
<TR><TD ALIGN=left NOWRAP><TT>member1@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>member2@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>member3@example.org</TT></TD>
|
|
</TR></TABLE></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Displayed groups</TD>
|
|
<TD ALIGN=left NOWRAP><TT>club_members</TT></TD>
|
|
</TR></TABLE>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
<LI CLASS="li-itemize">In another case we have a company which has three divisions: Management,
|
|
Marketing and Sales. All group members should see all other members in their
|
|
rosters. Additonally, all managers should have all marketing and sales people
|
|
in their roster. Simultaneously, all marketeers and the whole sales team
|
|
should see all managers. This scenario can be achieved by creating shared
|
|
roster groups as shown in the following table:
|
|
<BLOCKQUOTE CLASS="table"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
<TABLE BORDER=1 CELLSPACING=0 CELLPADDING=1>
|
|
<TR><TD ALIGN=left NOWRAP>Identification</TD>
|
|
<TD ALIGN=left NOWRAP>Group `<TT>management</TT>'</TD>
|
|
<TD ALIGN=left NOWRAP>Group `<TT>marketing</TT>'</TD>
|
|
<TD ALIGN=left NOWRAP>Group `<TT>sales</TT>'</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Name</TD>
|
|
<TD ALIGN=left NOWRAP>Management</TD>
|
|
<TD ALIGN=left NOWRAP>Marketing</TD>
|
|
<TD ALIGN=left NOWRAP>Sales</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Description</TD>
|
|
<TD ALIGN=left NOWRAP> </TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Members</TD>
|
|
<TD ALIGN=left NOWRAP><TABLE CELLSPACING=2 CELLPADDING=0>
|
|
<TR><TD ALIGN=left NOWRAP><TT>manager1@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>manager2@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>manager3@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>manager4@example.org</TT></TD>
|
|
</TR></TABLE>
|
|
</TD>
|
|
<TD ALIGN=left NOWRAP><TABLE CELLSPACING=2 CELLPADDING=0>
|
|
<TR><TD ALIGN=left NOWRAP><TT>marketeer1@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>marketeer2@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>marketeer3@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>marketeer4@example.org</TT></TD>
|
|
</TR></TABLE>
|
|
</TD>
|
|
<TD ALIGN=left NOWRAP><TABLE CELLSPACING=2 CELLPADDING=0>
|
|
<TR><TD ALIGN=left NOWRAP><TT>saleswoman1@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>salesman1@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>saleswoman2@example.org</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>salesman2@example.org</TT></TD>
|
|
</TR></TABLE></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>Displayed groups</TD>
|
|
<TD ALIGN=left NOWRAP><TABLE CELLSPACING=2 CELLPADDING=0>
|
|
<TR><TD ALIGN=left NOWRAP><TT>management</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>marketing</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>sales</TT></TD>
|
|
</TR></TABLE>
|
|
</TD>
|
|
<TD ALIGN=left NOWRAP><TABLE CELLSPACING=2 CELLPADDING=0>
|
|
<TR><TD ALIGN=left NOWRAP><TT>management</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>marketing</TT></TD>
|
|
</TR></TABLE>
|
|
</TD>
|
|
<TD ALIGN=left NOWRAP><TABLE CELLSPACING=2 CELLPADDING=0>
|
|
<TR><TD ALIGN=left NOWRAP><TT>management</TT></TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP><TT>sales</TT></TD>
|
|
</TR></TABLE></TD>
|
|
</TR></TABLE>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
</UL>
|
|
<!--TOC subsection <TT>mod_stats</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc65">5.18</A> <A NAME="modstats"><TT>mod_stats</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modstats"></A>
|
|
|
|
This module adds support for Statistics Gathering (<A HREF="http://www.jabber.org/jeps/jep-0039.html">JEP-0039</A>). This protocol
|
|
allows you to retrieve next statistics from your <TT>ejabberd</TT> deployment:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Total number of registered users on the current virtual host (users/total).
|
|
<LI CLASS="li-itemize">Total number of registered users on all virtual hosts (users/all-hosts/total).
|
|
<LI CLASS="li-itemize">Total number of online users on the current virtual host (users/online).
|
|
<LI CLASS="li-itemize">Total number of online users on all virtual hosts (users/all-hosts/online).
|
|
</UL>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Statistics Gathering (<TT>http://jabber.org/protocol/stats</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
As there are only a small amount of clients (for example
|
|
<A HREF="http://tkabber.jabber.ru/">Tkabber</A>) and software libraries with
|
|
support for this JEP, a few examples are given of the XML you need to send
|
|
in order to get the statistics. Here they are:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
You can request the number of online users on the current virtual host
|
|
(<TT>example.org</TT>) by sending:
|
|
<PRE CLASS="verbatim">
|
|
<iq to='example.org' type='get'>
|
|
<query xmlns='http://jabber.org/protocol/stats'>
|
|
<stat name='users/online'/>
|
|
</query>
|
|
</iq>
|
|
</PRE><LI CLASS="li-itemize">You can request the total number of registered users on all virtual hosts
|
|
by sending:
|
|
<PRE CLASS="verbatim">
|
|
<iq to='example.org' type='get'>
|
|
<query xmlns='http://jabber.org/protocol/stats'>
|
|
<stat name='users/all-hosts/total'/>
|
|
</query>
|
|
</iq>
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_time</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc66">5.19</A> <A NAME="modtime"><TT>mod_time</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modtime"></A>
|
|
|
|
This module features support for Entity Time (<A HREF="http://www.jabber.org/jeps/jep-0090.html">JEP-0090</A>). By using this JEP,
|
|
you are able to discover the time at another entity's location.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Entity Time (<TT>jabber:iq:time</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
<!--TOC subsection <TT>mod_vcard</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc67">5.20</A> <A NAME="modvcard"><TT>mod_vcard</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modvcard"></A>
|
|
|
|
This module allows end users to store and retrieve their vCard, and to retrieve
|
|
other users vCards, as defined in vcard-temp (<A HREF="http://www.jabber.org/jeps/jep-0054.html">JEP-0054</A>). The module also
|
|
implements an uncomplicated Jabber User Directory based on the vCards of
|
|
these users. Moreover, it enables the server to send its vCard when queried.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
|
|
<B><TT>hosts</TT></B><DD CLASS="dd-description"> This option defines the hostnames of the
|
|
service (see section <A HREF="#sec:modhostsoption">5.2.2</A>). If neither <TT>hosts</TT> nor
|
|
the old <TT>host</TT> is present, the prefix `<TT>vjud.</TT>' is added to all
|
|
<TT>ejabberd</TT> hostnames.
|
|
|
|
<DT CLASS="dt-description"><B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for <TT>vcard-temp</TT> IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
<DT CLASS="dt-description"><B><TT>search</TT></B><DD CLASS="dd-description">This option specifies whether the search
|
|
functionality is enabled (value: <TT>true</TT>) or disabled (value:
|
|
<TT>false</TT>). If disabled, the option <TT>hosts</TT> will be ignored and the
|
|
Jabber User Directory service will not appear in the Service Discovery item
|
|
list. The default value is <TT>true</TT>.
|
|
<DT CLASS="dt-description"><B><TT>matches</TT></B><DD CLASS="dd-description">With this option, the number of reported
|
|
search results can be limited. If the option's value is set to <TT>infinity</TT>,
|
|
all search results are reported. The default value is <TT>30</TT>.
|
|
<DT CLASS="dt-description"><B><TT>allow_return_all</TT></B><DD CLASS="dd-description">This option enables
|
|
you to specify if search operations with empty input fields should return all
|
|
users who added some information to their vCard. The default value is
|
|
<TT>false</TT>.
|
|
<DT CLASS="dt-description"><B><TT>search_all_hosts</TT></B><DD CLASS="dd-description">If this option is set
|
|
to <TT>true</TT>, search operations will apply to all virtual hosts. Otherwise
|
|
only the current host will be searched. The default value is <TT>true</TT>.
|
|
</DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
In this first situation, search results are limited to twenty items,
|
|
every user who added information to their vCard will be listed when people
|
|
do an empty search, and only users from the current host will be returned:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_vcard, [{search, true},
|
|
{matches, 20},
|
|
{allow_return_all, true},
|
|
{search_all_hosts, false}]},
|
|
...
|
|
]}.
|
|
</PRE><LI CLASS="li-itemize">The second situation differs in a way that search results are not limited,
|
|
and that all virtual hosts will be searched instead of only the current one:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
[
|
|
...
|
|
{mod_vcard, [{search, true},
|
|
{matches, infinity},
|
|
{allow_return_all, true}]},
|
|
...
|
|
]}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_vcard_ldap</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc68">5.21</A> <A NAME="modvcardldap"><TT>mod_vcard_ldap</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modvcardldap"></A>
|
|
|
|
<TT>ejabberd</TT> can map LDAP attributes to vCard fields. This behaviour is
|
|
implemented in the <TT>mod_vcard_ldap</TT> module. This module does not depend on the
|
|
authentication method (see <A HREF="#sec:ldapauth">4.5.2</A>). The <TT>mod_vcard_ldap</TT> module
|
|
has its own optional parameters. The first group of parameters has the same
|
|
meaning as the top-level LDAP parameters to set the authentication method:
|
|
<TT>ldap_servers</TT>, <TT>ldap_port</TT>, <TT>ldap_rootdn</TT>,
|
|
<TT>ldap_password</TT>, <TT>ldap_base</TT>, <TT>ldap_uidattr</TT>,
|
|
<TT>ldap_uidattr_format</TT> and <TT>ldap_filter</TT>. See
|
|
section <A HREF="#sec:ldapauth">4.5.2</A> for detailed information about these options. If one
|
|
of these options is not set, <TT>ejabberd</TT> will look for the top-level option with
|
|
the same name. The second group of parameters consists of the following
|
|
<TT>mod_vcard_ldap</TT>-specific options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
|
|
<B><TT>hosts</TT></B><DD CLASS="dd-description"> This option defines the hostnames of the
|
|
service (see section <A HREF="#sec:modhostsoption">5.2.2</A>). If neither <TT>hosts</TT> nor
|
|
the old <TT>host</TT> is present, the prefix `<TT>vjud.</TT>' is added to all
|
|
<TT>ejabberd</TT> hostnames.
|
|
|
|
<DT CLASS="dt-description"><B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for <TT>vcard-temp</TT> IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
<DT CLASS="dt-description"><B><TT>search</TT></B><DD CLASS="dd-description">This option specifies whether the search
|
|
functionality is enabled (value: <TT>true</TT>) or disabled (value:
|
|
<TT>false</TT>). If disabled, the option <TT>hosts</TT> will be ignored and the
|
|
Jabber User Directory service will not appear in the Service Discovery item
|
|
list. The default value is <TT>true</TT>.
|
|
<DT CLASS="dt-description"><B><TT>ldap_vcard_map</TT></B><DD CLASS="dd-description">With this option you can
|
|
set the table that maps LDAP attributes to vCard fields. The format is:
|
|
<TT>[Name_of_vCard_field, Pattern, List_of_LDAP_attributes, ...]</TT>.
|
|
<TT>Name_of_vcard_field</TT> is the type name of the vCard as defined in
|
|
<A HREF="http://www.ietf.org/rfc/rfc2426.txt">RFC 2426</A>. <TT>Pattern</TT> is a
|
|
string which contains pattern variables <TT>"%u"</TT>, <TT>"%d"</TT> or
|
|
<TT>"%s"</TT>. <TT>List_of_LDAP_attributes</TT> is the list containing LDAP
|
|
attributes. The pattern variables <TT>"%s"</TT> will be sequentially replaced
|
|
with the values of LDAP attributes from <TT>List_of_LDAP_attributes</TT>,
|
|
<TT>"%u"</TT> will be replaced with the user part of a JID, and <TT>"%d"</TT>
|
|
will be replaced with the domain part of a JID. The default is:
|
|
<PRE CLASS="verbatim">
|
|
[{"NICKNAME", "%u", []},
|
|
{"FN", "%s", ["displayName"]},
|
|
{"FAMILY", "%s", ["sn"]},
|
|
{"GIVEN", "%s", ["givenName"]},
|
|
{"MIDDLE", "%s", ["initials"]},
|
|
{"ORGNAME", "%s", ["o"]},
|
|
{"ORGUNIT", "%s", ["ou"]},
|
|
{"CTRY", "%s", ["c"]},
|
|
{"LOCALITY", "%s", ["l"]},
|
|
{"STREET", "%s", ["street"]},
|
|
{"REGION", "%s", ["st"]},
|
|
{"PCODE", "%s", ["postalCode"]},
|
|
{"TITLE", "%s", ["title"]},
|
|
{"URL", "%s", ["labeleduri"]},
|
|
{"DESC", "%s", ["description"]},
|
|
{"TEL", "%s", ["telephoneNumber"]},
|
|
{"EMAIL", "%s", ["mail"]},
|
|
{"BDAY", "%s", ["birthDay"]},
|
|
{"ROLE", "%s", ["employeeType"]},
|
|
{"PHOTO", "%s", ["jpegPhoto"]}]
|
|
</PRE><DT CLASS="dt-description"><B><TT>ldap_search_fields</TT></B><DD CLASS="dd-description">This option
|
|
defines the search form and the LDAP attributes to search within. The format
|
|
is: <TT>[Name, Attribute, ...]</TT>. <TT>Name</TT> is the name of a search form
|
|
field which will be automatically translated by using the translation
|
|
files (see <TT>msgs/*.msg</TT> for available words). <TT>Attribute</TT> is the
|
|
LDAP attribute or the pattern <TT>"%u"</TT>. The default is:
|
|
<PRE CLASS="verbatim">
|
|
[{"User", "%u"},
|
|
{"Full Name", "displayName"},
|
|
{"Given Name", "givenName"},
|
|
{"Middle Name", "initials"},
|
|
{"Family Name", "sn"},
|
|
{"Nickname", "%u"},
|
|
{"Birthday", "birthDay"},
|
|
{"Country", "c"},
|
|
{"City", "l"},
|
|
{"Email", "mail"},
|
|
{"Organization Name", "o"},
|
|
{"Organization Unit", "ou"}]
|
|
</PRE><DT CLASS="dt-description"><B><TT>ldap_search_reported</TT></B><DD CLASS="dd-description">This option
|
|
defines which search fields should be reported. The format is:
|
|
<TT>[Name, vCard_Name, ...]</TT>. <TT>Name</TT> is the name of a search form
|
|
field which will be automatically translated by using the translation
|
|
files (see <TT>msgs/*.msg</TT> for available words). <TT>vCard_Name</TT> is the
|
|
vCard field name defined in the <TT>ldap_vcard_map</TT> option. The default
|
|
is:
|
|
<PRE CLASS="verbatim">
|
|
[{"Full Name", "FN"},
|
|
{"Given Name", "GIVEN"},
|
|
{"Middle Name", "MIDDLE"},
|
|
{"Family Name", "FAMILY"},
|
|
{"Nickname", "NICKNAME"},
|
|
{"Birthday", "BDAY"},
|
|
{"Country", "CTRY"},
|
|
{"City", "LOCALITY"},
|
|
{"Email", "EMAIL"},
|
|
{"Organization Name", "ORGNAME"},
|
|
{"Organization Unit", "ORGUNIT"}]
|
|
</PRE></DL>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
<BR>
|
|
<BR>
|
|
Let's say <TT>ldap.example.org</TT> is the name of our LDAP server. We have
|
|
users with their passwords in <TT>"ou=Users,dc=example,dc=org"</TT> directory.
|
|
Also we have addressbook, which contains users emails and their additional
|
|
infos in <TT>"ou=AddressBook,dc=example,dc=org"</TT> directory. Corresponding
|
|
authentication section should looks like this:
|
|
<PRE CLASS="verbatim">
|
|
%% authentication method
|
|
{auth_method, ldap}.
|
|
%% DNS name of our LDAP server
|
|
{ldap_servers, ["ldap.example.org"]}.
|
|
%% We want to authorize users from 'shadowAccount' object class only
|
|
{ldap_filter, "(objectClass=shadowAccount)"}.
|
|
</PRE>
|
|
Now we want to use users LDAP-info as their vCards. We have four attributes
|
|
defined in our LDAP schema: <TT>"mail"</TT> — email address, <TT>"givenName"</TT>
|
|
— first name, <TT>"sn"</TT> — second name, <TT>"birthDay"</TT> — birthday.
|
|
Also we want users to search each other. Let's see how we can set it up:
|
|
<PRE CLASS="verbatim">
|
|
{modules,
|
|
...
|
|
{mod_vcard_ldap,
|
|
[
|
|
%% We use the same server and port, but want to bind anonymously because
|
|
%% our LDAP server accepts anonymous requests to
|
|
%% "ou=AddressBook,dc=example,dc=org" subtree.
|
|
{ldap_rootdn, ""},
|
|
{ldap_password, ""},
|
|
%% define the addressbook's base
|
|
{ldap_base, "ou=AddressBook,dc=example,dc=org"},
|
|
%% user's part of JID is located in the "mail" attribute
|
|
{ldap_uidattr, "mail"},
|
|
%% common format for our emails
|
|
{ldap_uidattr_format, "%u@mail.example.org"},
|
|
%% We have to define empty filter here, because entries in addressbook does not
|
|
%% belong to shadowAccount object class
|
|
{ldap_filter, ""},
|
|
%% Now we want to define vCard pattern
|
|
{ldap_vcard_map,
|
|
[{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname
|
|
{"GIVEN", "%s", ["givenName"]},
|
|
{"FAMILY", "%s", ["sn"]},
|
|
{"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John"
|
|
{"EMAIL", "%s", ["mail"]},
|
|
{"BDAY", "%s", ["birthDay"]}]},
|
|
%% Search form
|
|
{ldap_search_fields,
|
|
[{"User", "%u"},
|
|
{"Name", "givenName"},
|
|
{"Family Name", "sn"},
|
|
{"Email", "mail"},
|
|
{"Birthday", "birthDay"}]},
|
|
%% vCard fields to be reported
|
|
%% Note that JID is always returned with search results
|
|
{ldap_search_reported,
|
|
[{"Full Name", "FN"},
|
|
{"Nickname", "NICKNAME"},
|
|
{"Birthday", "BDAY"}]}
|
|
]}
|
|
...
|
|
}.
|
|
</PRE>
|
|
Note that <TT>mod_vcard_ldap</TT> module checks an existence of the user before
|
|
searching his info in LDAP.<BR>
|
|
<BR>
|
|
<LI CLASS="li-itemize"><TT>ldap_vcard_map</TT> example:
|
|
<PRE CLASS="verbatim">
|
|
{ldap_vcard_map,
|
|
[{"NICKNAME", "%u", []},
|
|
{"FN", "%s", ["displayName"]},
|
|
{"CTRY", "Russia", []},
|
|
{"EMAIL", "%u@%d", []},
|
|
{"DESC", "%s\n%s", ["title", "description"]}
|
|
]},
|
|
</PRE><LI CLASS="li-itemize"><TT>ldap_search_fields</TT> example:
|
|
<PRE CLASS="verbatim">
|
|
{ldap_search_fields,
|
|
[{"User", "uid"},
|
|
{"Full Name", "displayName"},
|
|
{"Email", "mail"}
|
|
]},
|
|
</PRE><LI CLASS="li-itemize"><TT>ldap_search_reported</TT> example:
|
|
<PRE CLASS="verbatim">
|
|
{ldap_search_reported,
|
|
[{"Full Name", "FN"},
|
|
{"Email", "EMAIL"},
|
|
{"Birthday", "BDAY"},
|
|
{"Nickname", "NICKNAME"}
|
|
]},
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>mod_version</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc69">5.22</A> <A NAME="modversion"><TT>mod_version</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:modversion"></A>
|
|
|
|
This module implements Software Version (<A HREF="http://www.jabber.org/jeps/jep-0092.html">JEP-0092</A>). Consequently, it
|
|
answers <TT>ejabberd</TT>'s version when queried.<BR>
|
|
<BR>
|
|
Options:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>iqdisc</TT></B><DD CLASS="dd-description"> This specifies
|
|
the processing discipline for Software Version (<TT>jabber:iq:version</TT>) IQ queries
|
|
(see section <A HREF="#sec:modiqdiscoption">5.2.1</A>).
|
|
</DL>
|
|
<!--TOC section Creating an Initial Administrator-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc70">6</A> <A NAME="initialadmin">Creating an Initial Administrator</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:initialadmin"></A>
|
|
Before the web interface can be entered to perform administration tasks, an
|
|
account with administrator rights is needed on your <TT>ejabberd</TT> deployment.<BR>
|
|
<BR>
|
|
Instructions to create an initial administrator account:
|
|
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
|
|
Register an account on your <TT>ejabberd</TT> deployment. An account can be
|
|
created in two ways:
|
|
<OL CLASS="enumerate" type=a><LI CLASS="li-enumerate">
|
|
Using the tool <TT>ejabberdctl</TT> (see
|
|
section <A HREF="#sec:ejabberdctl">7.2</A>):
|
|
<PRE CLASS="verbatim">
|
|
% ejabberdctl node@host register admin example.org password
|
|
</PRE><LI CLASS="li-enumerate">Using In-Band Registration (see section <A HREF="#sec:modregister">5.14</A>): you can
|
|
use a Jabber client to register an account.
|
|
</OL>
|
|
<LI CLASS="li-enumerate">Edit the configuration file to promote the account created in the previous
|
|
step to an account with administrator rights. Note that if you want to add
|
|
more administrators, a seperate acl entry is needed for each administrator.
|
|
<PRE CLASS="verbatim">
|
|
{acl, admins, {user, "admin", "example.org"}}.
|
|
{access, configure, [{allow, admins}]}.
|
|
</PRE><LI CLASS="li-enumerate">Restart <TT>ejabberd</TT> to load the new configuration.
|
|
<LI CLASS="li-enumerate">Open the web interface (<CODE>http://server:port/admin/</CODE>) in your
|
|
favourite browser. Make sure to enter the <EM>full</EM> JID as username (in this
|
|
example: <TT>admin@example.org</TT>. The reason that you also need to enter the
|
|
suffix, is because <TT>ejabberd</TT>'s virtual hosting support.
|
|
</OL>
|
|
<!--TOC section Online Configuration and Monitoring-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc71">7</A> <A NAME="onlineconfig">Online Configuration and Monitoring</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:onlineconfig"></A>
|
|
<!--TOC subsection Web Interface-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc72">7.1</A> <A NAME="webinterface">Web Interface</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:webinterface"></A>
|
|
|
|
To perform online configuration of <TT>ejabberd</TT> you need to enable the
|
|
<TT>ejabberd_http</TT> listener with the option <TT>web_admin</TT> (see
|
|
section <A HREF="#sec:listened">3.3</A>). Then you can open
|
|
<CODE>http://server:port/admin/</CODE> in your favourite web browser. You
|
|
will be asked to enter the username (the <EM>full</EM> Jabber ID) and password
|
|
of an <TT>ejabberd</TT> user with administrator rights. After authentication
|
|
you will see a page similar to figure <A HREF="#fig:webadmmain">1</A>.
|
|
<BLOCKQUOTE CLASS="figure"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
|
|
<IMG SRC="webadmmain.png" ALT="webadmmain.png">
|
|
|
|
|
|
<BR>
|
|
<BR>
|
|
<DIV CLASS="center">Figure 1: Top page from the web interface</DIV><BR>
|
|
<BR>
|
|
|
|
<A NAME="fig:webadmmain"></A>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
Here you can edit access restrictions, manage users, create backups,
|
|
manage the database, enable/disable ports listened for, view server
|
|
statistics,...<BR>
|
|
<BR>
|
|
Examples:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
You can serve the web interface on the same port as the
|
|
HTTP Polling interface. In this example
|
|
you should point your web browser to <CODE>http://example.org:5280/admin/</CODE> to
|
|
administer all virtual hosts or to
|
|
<CODE>http://example.org:5280/admin/server/example.com/</CODE> to administer only
|
|
the virtual host <TT>example.com</TT>. Before you get access to the web interface
|
|
you need to enter as username, the JID and password from a registered user
|
|
that is allowed to configure <TT>ejabberd</TT>. In this example you can enter as
|
|
username `<TT>admin@example.net</TT>' to administer all virtual hosts (first
|
|
URL). If you log in with `<TT>admin@example.com</TT>' on<BR>
|
|
<CODE>http://example.org:5280/admin/server/example.com/</CODE> you can only
|
|
administer the virtual host <TT>example.com</TT>.
|
|
<PRE CLASS="verbatim">
|
|
...
|
|
{acl, admins, {user, "admin", "example.net"}}.
|
|
{host_config, "example.com", [{acl, admins, {user, "admin", "example.com"}}]}.
|
|
{access, configure, [{allow, admins}]}.
|
|
...
|
|
{hosts, ["example.org"]}.
|
|
...
|
|
{listen,
|
|
[...
|
|
{5280, ejabberd_http, [http_poll, web_admin]},
|
|
...
|
|
]
|
|
}.
|
|
</PRE><LI CLASS="li-itemize">For security reasons, you can serve the web interface on a secured
|
|
connection, on a port differing from the HTTP Polling interface, and bind it
|
|
to the internal LAN IP. The web interface will be accessible by pointing your
|
|
web browser to <CODE>https://192.168.1.1:5280/admin/</CODE>:
|
|
<PRE CLASS="verbatim">
|
|
...
|
|
{hosts, ["example.org"]}.
|
|
...
|
|
{listen,
|
|
[...
|
|
{5270, ejabberd_http, [http_poll]},
|
|
{5280, ejabberd_http, [web_admin, {ip, {192, 168, 1, 1}},
|
|
tls, {certfile, "/usr/local/etc/server.pem"}]},
|
|
...
|
|
]
|
|
}.
|
|
</PRE></UL>
|
|
<!--TOC subsection <TT>ejabberdctl</TT>-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc73">7.2</A> <A NAME="ejabberdctl"><TT>ejabberdctl</TT></A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:ejabberdctl"></A>
|
|
|
|
It is possible to do some administration operations using the command
|
|
line tool <TT>ejabberdctl</TT>. You can list all available options by
|
|
running <TT>ejabberdctl</TT> without arguments:
|
|
<PRE CLASS="verbatim">
|
|
% ejabberdctl
|
|
Usage: ejabberdctl node command
|
|
|
|
Available commands:
|
|
status get ejabberd status
|
|
stop stop ejabberd
|
|
restart restart ejabberd
|
|
reopen-log reopen log file
|
|
register user server password register a user
|
|
unregister user server unregister a user
|
|
backup file store a database backup to file
|
|
restore file restore a database backup from file
|
|
install-fallback file install a database fallback from file
|
|
dump file dump a database to a text file
|
|
load file restore a database from a text file
|
|
import-file file import user data from jabberd 1.4 spool file
|
|
import-dir dir import user data from jabberd 1.4 spool directory
|
|
registered-users list all registered users
|
|
delete-expired-messages delete expired offline messages from database
|
|
|
|
Example:
|
|
ejabberdctl ejabberd@host restart
|
|
</PRE>
|
|
Additional information:
|
|
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
|
|
<B><TT>reopen-log </TT></B><DD CLASS="dd-description"> If you use a tool to rotate logs, you have to configure it
|
|
so that this command is executed after each rotation.
|
|
<DT CLASS="dt-description"><B><TT>backup, restore, install-fallback, dump, load</TT></B><DD CLASS="dd-description"> You can use these
|
|
commands to create and restore backups.
|
|
<DT CLASS="dt-description"><B><TT>import-file, import-dir</TT></B><DD CLASS="dd-description">
|
|
These options can be used to migrate from other Jabber/XMPP servers. There
|
|
exist tutorials to <A HREF="http://ejabberd.jabber.ru/migrate-to-ejabberd">migrate from other software to ejabberd</A>.
|
|
<DT CLASS="dt-description"><B><TT>delete-expired-messages</TT></B><DD CLASS="dd-description"> This option can be used to delete old messages
|
|
in offline storage. This might be useful when the number of offline messages
|
|
is very high.
|
|
</DL>
|
|
<!--TOC section Firewall Settings-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc74">8</A> <A NAME="firewall">Firewall Settings</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:firewall"></A>
|
|
|
|
You need to take the following TCP ports in mind when configuring your firewall:
|
|
<BLOCKQUOTE CLASS="table"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
<TABLE BORDER=1 CELLSPACING=0 CELLPADDING=1>
|
|
<TR><TD ALIGN=left NOWRAP>Port</TD>
|
|
<TD ALIGN=left NOWRAP>Description</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>5222</TD>
|
|
<TD ALIGN=left NOWRAP>SASL and unencrypted c2s connections.</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>5223</TD>
|
|
<TD ALIGN=left NOWRAP>Obsolete SSL c2s connections.</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>5269</TD>
|
|
<TD ALIGN=left NOWRAP>s2s connections.</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>4369</TD>
|
|
<TD ALIGN=left NOWRAP>Only for clustering (see <A HREF="#sec:clustering">10</A>).</TD>
|
|
</TR>
|
|
<TR><TD ALIGN=left NOWRAP>port range</TD>
|
|
<TD ALIGN=left NOWRAP>Only for clustring (see <A HREF="#sec:clustering">10</A>). This range
|
|
is configurable (see <A HREF="#sec:start">2.4</A>).</TD>
|
|
</TR></TABLE>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
<!--TOC section SRV Records-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc75">9</A> <A NAME="srv">SRV Records</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:srv"></A>
|
|
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
General information:
|
|
<A HREF="http://en.wikipedia.org/wiki/SRV_record">SRV record</A>
|
|
<LI CLASS="li-itemize">Practical information:
|
|
<A HREF="http://jabberd.jabberstudio.org/2/docs/section05.html#5_7">Setting DNS SRV Records</A>
|
|
</UL>
|
|
<!--TOC section Clustering-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc76">10</A> <A NAME="clustering">Clustering</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:clustering"></A>
|
|
|
|
<!--TOC subsection How it Works-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc77">10.1</A> <A NAME="howitworks">How it Works</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:howitworks"></A>
|
|
|
|
A Jabber domain is served by one or more <TT>ejabberd</TT> nodes. These nodes can
|
|
be run on different machines that are connected via a network. They all
|
|
must have the ability to connect to port 4369 of all another nodes, and must
|
|
have the same magic cookie (see Erlang/OTP documentation, in other words the
|
|
file <TT>~ejabberd/.erlang.cookie</TT> must be the same on all nodes). This is
|
|
needed because all nodes exchange information about connected users, s2s
|
|
connections, registered services, etc...<BR>
|
|
<BR>
|
|
Each <TT>ejabberd</TT> node has the following modules:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
router,
|
|
<LI CLASS="li-itemize">local router,
|
|
<LI CLASS="li-itemize">session manager,
|
|
<LI CLASS="li-itemize">s2s manager.
|
|
</UL>
|
|
<!--TOC subsubsection Router-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc78">10.1.1</A> <A NAME="router">Router</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:router"></A>
|
|
|
|
This module is the main router of Jabber packets on each node. It
|
|
routes them based on their destination's domains. It uses a global
|
|
routing table. The domain of the packet's destination is searched in the
|
|
routing table, and if it is found, the packet is routed to the
|
|
appropriate process. If not, it is sent to the s2s manager.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Local Router-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc79">10.1.2</A> <A NAME="localrouter">Local Router</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:localrouter"></A>
|
|
|
|
This module routes packets which have a destination domain equal to
|
|
one of this server's host names. If the destination JID has a non-empty user
|
|
part, it is routed to the session manager, otherwise it is processed depending
|
|
on its content.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection Session Manager-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc80">10.1.3</A> <A NAME="sessionmanager">Session Manager</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:sessionmanager"></A>
|
|
|
|
This module routes packets to local users. It looks up to which user
|
|
resource a packet must be sent via a presence table. Then the packet is
|
|
either routed to the appropriate c2s process, or stored in offline
|
|
storage, or bounced back.<BR>
|
|
<BR>
|
|
<!--TOC subsubsection s2s Manager-->
|
|
|
|
<H4 CLASS="subsubsection"><A NAME="htoc81">10.1.4</A> <A NAME="s2smanager">s2s Manager</A></H4><!--SEC END -->
|
|
|
|
<A NAME="sec:s2smanager"></A>
|
|
|
|
This module routes packets to other Jabber servers. First, it
|
|
checks if an opened s2s connection from the domain of the packet's
|
|
source to the domain of the packet's destination exists. If that is the case,
|
|
the s2s manager routes the packet to the process
|
|
serving this connection, otherwise a new connection is opened.<BR>
|
|
<BR>
|
|
<!--TOC subsection Clustering Setup-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc82">10.2</A> <A NAME="cluster">Clustering Setup</A></H3><!--SEC END -->
|
|
|
|
<A NAME="sec:cluster"></A>
|
|
|
|
Suppose you already configured <TT>ejabberd</TT> on one machine named (<TT>first</TT>),
|
|
and you need to setup another one to make an <TT>ejabberd</TT> cluster. Then do
|
|
following steps:
|
|
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
|
|
Copy <CODE>~ejabberd/.erlang.cookie</CODE> file from <TT>first</TT> to
|
|
<TT>second</TT>.<BR>
|
|
<BR>
|
|
(alt) You can also add `<CODE>-cookie content_of_.erlang.cookie</CODE>'
|
|
option to all `<TT>erl</TT>' commands below.<BR>
|
|
<BR>
|
|
<LI CLASS="li-enumerate">On <TT>second</TT> run the following command as the <TT>ejabberd</TT> daemon user,
|
|
in the working directory of <TT>ejabberd</TT>:
|
|
<PRE CLASS="verbatim">
|
|
erl -sname ejabberd \
|
|
-mnesia extra_db_nodes "['ejabberd@first']" \
|
|
-s mnesia
|
|
</PRE>
|
|
This will start Mnesia serving the same database as <TT>ejabberd@first</TT>.
|
|
You can check this by running the command `<CODE>mnesia:info().</CODE>'. You
|
|
should see a lot of remote tables and a line like the following:
|
|
<PRE CLASS="verbatim">
|
|
running db nodes = [ejabberd@first, ejabberd@second]
|
|
</PRE><BR>
|
|
<BR>
|
|
<LI CLASS="li-enumerate">Now run the following in the same `<TT>erl</TT>' session:
|
|
<PRE CLASS="verbatim">
|
|
mnesia:change_table_copy_type(schema, node(), disc_copies).
|
|
</PRE>
|
|
This will create local disc storage for the database.<BR>
|
|
<BR>
|
|
(alt) Change storage type of the <TT>scheme</TT> table to `RAM and disc
|
|
copy' on the second node via the web interface.<BR>
|
|
<BR>
|
|
<LI CLASS="li-enumerate">Now you can add replicas of various tables to this node with
|
|
`<CODE>mnesia:add_table_copy</CODE>' or
|
|
`<CODE>mnesia:change_table_copy_type</CODE>' as above (just replace
|
|
`<CODE>schema</CODE>' with another table name and `<CODE>disc_copies</CODE>'
|
|
can be replaced with `<CODE>ram_copies</CODE>' or
|
|
`<CODE>disc_only_copies</CODE>').<BR>
|
|
<BR>
|
|
Which tables to replicate is very dependant on your needs, you can get
|
|
some hints from the command `<CODE>mnesia:info().</CODE>', by looking at the
|
|
size of tables and the default storage type for each table on 'first'.<BR>
|
|
<BR>
|
|
Replicating a table makes lookups in this table faster on this node.
|
|
Writing, on the other hand, will be slower. And of course if machine with one
|
|
of the replicas is down, other replicas will be used.<BR>
|
|
<BR>
|
|
Also <A HREF="http://www.erlang.se/doc/doc-5.4.9/lib/mnesia-4.2.2/doc/html/Mnesia_chap5.html#5.3">section 5.3 (Table Fragmentation) of Mnesia User's Guide</A> can be helpful.
|
|
<BR>
|
|
<BR>
|
|
(alt) Same as in previous item, but for other tables.<BR>
|
|
<BR>
|
|
<LI CLASS="li-enumerate">Run `<CODE>init:stop().</CODE>' or just `<CODE>q().</CODE>' to exit from
|
|
the Erlang shell. This probably can take some time if Mnesia has not yet
|
|
transfered and processed all data it needed from <TT>first</TT>.<BR>
|
|
<BR>
|
|
<LI CLASS="li-enumerate">Now run <TT>ejabberd</TT> on <TT>second</TT> with almost the same config as
|
|
on <TT>first</TT> (you probably do not need to duplicate `<CODE>acl</CODE>'
|
|
and `<CODE>access</CODE>' options — they will be taken from
|
|
<TT>first</TT>, and <CODE>mod_muc</CODE> and <CODE>mod_irc</CODE> should be
|
|
enabled only on one machine in the cluster).
|
|
</OL>
|
|
You can repeat these steps for other machines supposed to serve this
|
|
domain.<BR>
|
|
<BR>
|
|
|
|
<!--TOC section Internationalization and Localization-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc83">A</A> <A NAME="i18nl10n">Internationalization and Localization</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:i18nl10n"></A>
|
|
|
|
All built-in modules support the <TT>xml:lang</TT> attribute inside IQ queries.
|
|
Figure <A HREF="#fig:discorus">2</A>, for example, shows the reply to the following query:
|
|
<PRE CLASS="verbatim">
|
|
<iq id='5'
|
|
to='example.org'
|
|
type='get'
|
|
xml:lang='ru'>
|
|
<query xmlns='http://jabber.org/protocol/disco#items'/>
|
|
</iq>
|
|
</PRE>
|
|
<BLOCKQUOTE CLASS="figure"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
|
|
<IMG SRC="discorus.png" ALT="discorus.png">
|
|
|
|
|
|
<BR>
|
|
<BR>
|
|
<DIV CLASS="center">Figure 2: Service Discovery when <TT>xml:lang='ru'</TT></DIV><BR>
|
|
<BR>
|
|
|
|
<A NAME="fig:discorus"></A>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
The web interface also supports the <CODE>Accept-Language</CODE> HTTP header (compare
|
|
figure <A HREF="#fig:webadmmainru">3</A> with figure <A HREF="#fig:webadmmain">1</A>)
|
|
<BLOCKQUOTE CLASS="figure"><DIV CLASS="center"><DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV>
|
|
|
|
<IMG SRC="webadmmainru.png" ALT="webadmmainru.png">
|
|
|
|
|
|
<BR>
|
|
<BR>
|
|
<DIV CLASS="center">Figure 3: Top page from the web interface with HTTP header
|
|
`Accept-Language: ru'</DIV><BR>
|
|
<BR>
|
|
|
|
<A NAME="fig:webadmmainru"></A>
|
|
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
|
|
<!--TOC section Release Notes-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc84">B</A> <A NAME="releasenotes">Release Notes</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:releasenotes"></A>
|
|
|
|
<!--TOC subsection ejabberd 0.9-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc85">B.1</A> ejabberd 0.9</H3><!--SEC END -->
|
|
|
|
<PRE CLASS="verbatim">
|
|
Release notes
|
|
ejabberd 0.9
|
|
|
|
This document describes the major new features of and changes to
|
|
ejabberd 0.9, compared to latest public release ejabber 0.7.5.
|
|
|
|
For more detailed information, please refer to ejabberd User
|
|
Guide.
|
|
|
|
|
|
Virtual Hosting
|
|
|
|
ejabberd now can host several domain on the same instance.
|
|
This option is enabled by using:
|
|
|
|
{hosts, ["erlang-projects.org", "erlang-fr.org"]}.
|
|
|
|
instead of the previous host directive.
|
|
|
|
Note that you are now using a list of hosts. The main one should
|
|
be the first listed. See migration section further in this release
|
|
note for details.
|
|
|
|
|
|
Shared Roster
|
|
|
|
Shared roster is a new feature that allow the ejabberd
|
|
administrator to add jabber user that will be present in the
|
|
roster of every users on the server.
|
|
Shared roster are enabled by adding:
|
|
|
|
{mod_shared_roster, []}
|
|
|
|
at the end of your module list in your ejabberd.cfg file.
|
|
|
|
|
|
PostgreSQL (ODBC) support
|
|
|
|
This feature is experimental and not yet properly documented. This
|
|
feature is released for testing purpose.
|
|
|
|
You need to have Erlang/OTP R10 to compile with ODBC on various
|
|
flavour of *nix. You should use Erlang/OTP R10B-4, as this task
|
|
has became easier with this release. It comes already build in
|
|
Erlang/OTP Microsoft Windows binary.
|
|
|
|
PostgreSQL support is enabled by using the following module in
|
|
ejabberd.cfg instead of their standard counterpart:
|
|
|
|
mod_last_odbc.erl
|
|
mod_offline_odbc.erl
|
|
mod_roster_odbc.erl
|
|
|
|
The database schema is located in the src/odbc/pq.sql file.
|
|
|
|
Look at the src/ejabberd.cfg.example file for more information on
|
|
how to configure ejabberd with odbc support. You can get support
|
|
on how to configure ejabberd with a relational database.
|
|
|
|
|
|
Migration from ejabberd 0.7.5
|
|
|
|
Migration is pretty straightforward as Mnesia database schema
|
|
conversions is handled automatically. Remember however that you
|
|
must backup your ejabberd database before migration.
|
|
|
|
Here are the following steps to proceed:
|
|
|
|
1. Stop your instance of ejabberd.
|
|
|
|
2. In ejabberd.cfg, define the host lists. Change the host
|
|
directive to the hosts one:
|
|
Before:
|
|
{host, "erlang-projects.org"}.
|
|
After:
|
|
{hosts, ["erlang-projects.org", "erlang-fr.org"]}.
|
|
Note that when you restart the server the existing users will be
|
|
affected to the first virtual host, so the order is important. You
|
|
should keep the previous hostname as the first virtual host.
|
|
|
|
3. Restart ejabberd.
|
|
|
|
|
|
Bugfixes
|
|
|
|
This release contains several bugfixes and architectural changes.
|
|
Please refer to the Changelog file supplied with this release for
|
|
details of all improvements in the ejabberd code.
|
|
</PRE>
|
|
<!--TOC subsection ejabberd 0.9.1-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc86">B.2</A> ejabberd 0.9.1</H3><!--SEC END -->
|
|
|
|
<PRE CLASS="verbatim">
|
|
Release notes
|
|
ejabberd 0.9.1
|
|
|
|
This document describes the main changes from [25]ejabberd 0.9.
|
|
|
|
The code can be downloaded from the [26]download page.
|
|
|
|
For more detailed information, please refer to ejabberd [27]User Guide.
|
|
|
|
|
|
Groupchat (Multi-user chat and IRC) improvements
|
|
|
|
The multi-user chat code has been improved to comply with the latest version
|
|
of Jabber Enhancement Proposal 0045.
|
|
|
|
The IRC (Internet Relay Chat) features now support WHOIS and USERINFO
|
|
requests.
|
|
|
|
|
|
Web interface
|
|
|
|
ejabberd modules management features have been added to the web interface.
|
|
They now allow to start or stop extension module without restarting the
|
|
ejabberd server.
|
|
|
|
|
|
Publish and subscribe
|
|
|
|
It is now possible to a subscribe node with a JabberID that includes a
|
|
resource.
|
|
|
|
|
|
Translations
|
|
|
|
A new script has been included to help translate ejabberd into new languages
|
|
and maintain existing translations.
|
|
|
|
As a result, ejabberd is now translating into 10 languages:
|
|
* Dutch
|
|
* English
|
|
* French
|
|
* German
|
|
* Polish
|
|
* Portuguese
|
|
* Russian
|
|
* Spanish
|
|
* Swedish
|
|
* Ukrainian
|
|
|
|
|
|
Migration
|
|
|
|
No changes have been made to the database. No particular conversion steps
|
|
are needed. However, you should backup your database before upgrading to a
|
|
new ejabberd version.
|
|
|
|
|
|
Bugfixes
|
|
|
|
This release contains several bugfixes and architectural changes. Please
|
|
refer to the Changelog file supplied with this release for details of all
|
|
improvements in the ejabberd code.
|
|
</PRE>
|
|
<!--TOC subsection ejabberd 0.9.8-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc87">B.3</A> ejabberd 0.9.8</H3><!--SEC END -->
|
|
|
|
<PRE CLASS="verbatim">
|
|
Release notes
|
|
ejabberd 0.9.8
|
|
2005-08-01
|
|
|
|
This document describes the main changes in ejabberd 0.9.8. This
|
|
version prepares the way for the release of ejabberd 1.0, which
|
|
is due later this year.
|
|
|
|
The code can be downloaded from the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/
|
|
|
|
For more detailed information, please refer to ejabberd User Guide
|
|
on the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/docs.html
|
|
|
|
|
|
Recent changes include....
|
|
|
|
|
|
Enhanced virtual hosting
|
|
|
|
Virtual hosting applies to many more setting options and
|
|
features and is transparent. Virtual hosting accepts different
|
|
parameters for different virtual hosts regarding the following
|
|
features: authentication method, access control lists and access
|
|
rules, users management, statistics, and shared roster. The web
|
|
interface gives access to each virtual host's parameters.
|
|
|
|
|
|
Enhanced Publish-Subscribe module
|
|
|
|
ejabberd's Publish-Subscribe module integrates enhancements
|
|
coming from J-EAI, an XMPP-based integration server built on
|
|
ejabberd. ejabberd thus supports Publish-Subscribe node
|
|
configuration. It is possible to define nodes that should be
|
|
persistent, and the number of items to persist. Besides that, it
|
|
is also possible to define various notification parameters, such
|
|
as the delivery of the payload with the notifications, and the
|
|
notification of subscribers when some changes occur on items.
|
|
Other examples are: the maximum size of the items payload, the
|
|
subscription approvers, the limitation of the notification to
|
|
online users only, etc.
|
|
|
|
|
|
Code reorganisation and update
|
|
|
|
- The mod_register module has been cleaned up.
|
|
- ODBC support has been updated and several bugs have been fixed.
|
|
|
|
|
|
Development API
|
|
|
|
To ease the work of Jabber/XMPP developers, a filter_packet hook
|
|
has been added. As a result it is possible to develop plugins to
|
|
filter or modify packets flowing through ejabberd.
|
|
|
|
|
|
Translations
|
|
|
|
- Translations have been updated to support the new Publish-Subscribe features.
|
|
- A new Brazilian Portuguese translation has been contributed.
|
|
|
|
|
|
Web interface
|
|
|
|
- The CSS stylesheet from the web interface is W3C compliant.
|
|
|
|
|
|
Installers
|
|
|
|
Installers are provided for Microsoft Windows and Linux/x86. The
|
|
Linux installer includes Erlang ASN.1 modules for LDAP
|
|
authentication support.
|
|
|
|
|
|
Bugfixes
|
|
|
|
- This release contains several bugfixes and architectural
|
|
changes. Among other bugfixes include improvements in LDAP
|
|
authentication. Please refer to the ChangeLog file supplied
|
|
with this release regarding all improvements in ejabberd.
|
|
|
|
|
|
References
|
|
|
|
The ejabberd feature sheet helps comparing with other Jabber/XMPP
|
|
servers:
|
|
http://www.process-one.net/en/projects/ejabberd/docs/features.pdf
|
|
|
|
Contributed tutorials of interest are:
|
|
- Migration from Jabberd1.4 to ejabberd:
|
|
http://ejabberd.jabber.ru/jabberd1-to-ejabberd
|
|
- Migration from Jabberd2 to ejabberd:
|
|
http://ejabberd.jabber.ru/jabberd2-to-ejabberd
|
|
- Transport configuration for connecting to other networks:
|
|
http://ejabberd.jabber.ru/tutorials-transports
|
|
|
|
END
|
|
|
|
</PRE>
|
|
<!--TOC subsection ejabberd 1.0.0-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc88">B.4</A> ejabberd 1.0.0</H3><!--SEC END -->
|
|
|
|
<PRE CLASS="verbatim">
|
|
Release Notes
|
|
ejabberd 1.0.0
|
|
14 December 2005
|
|
|
|
This document describes the main changes in ejabberd 1.0.0. Unique in this
|
|
version is the compliancy with the XMPP (eXtensible Messaging and Presence
|
|
Protocol) standard. ejabberd is the first Open Source Jabber server claiming
|
|
to fully comply to the XMPP standard.
|
|
|
|
ejabberd can be downloaded from the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/
|
|
|
|
Detailed information can be found in the ejabberd Feature Sheet and User
|
|
Guide which are available on the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/docs.html
|
|
|
|
|
|
Recent changes include:
|
|
|
|
|
|
Server-to-server Encryption for Enhanced Security
|
|
|
|
- Support for STARTTLS and SASL EXTERNAL to secure server-to-server traffic
|
|
has been added.
|
|
- Also, STARTTLS and Dialback has been implemented for server-to-server (s2s)
|
|
connections. Detailed information about these new features can be found on
|
|
http://ejabberd.jabber.ru/s2s-encryption
|
|
- commonName and dNSName fields matching were introduced to ease the process
|
|
of retrieving certificates.
|
|
- Different certificates can be defined for each virtual host.
|
|
|
|
ODBC Support
|
|
|
|
- ODBC support has been improved to allow production use of ejabberd with
|
|
relational databases.
|
|
- Support for vCard storage in ODBC has been added.
|
|
- ejd2odbc.erl is a tool to convert an installation from Erlang's database
|
|
Mnesia to an ODBC compatible relational database.
|
|
|
|
Native PostgreSQL Support
|
|
|
|
- Native PostgreSQL support gives you a better performance when you use
|
|
PostgreSQL.
|
|
|
|
Shared Roster groups
|
|
|
|
- Shared Roster groups support has been enhanced. New is the ability to add
|
|
all registered users to everyone's roster. Detailed information about this
|
|
new feature can be found on http://ejabberd.jabber.ru/shared-roster-all
|
|
|
|
Web Interface
|
|
|
|
- The web interface internal code has been modified for better integration
|
|
and compliancy with J-EAI, an ejabberd-based Enterprise Application
|
|
Integration platform.
|
|
- More XHTML 1.0 Transitional compliancy work was done.
|
|
|
|
Transports
|
|
|
|
- A transport workaround can be enabled during compilation. To do this, you
|
|
can pass the "--enable-roster-gateway-workaround" option to the configure
|
|
script. (./configure --enable-roster-gateway-workaround)
|
|
This option allows transports to add items with subscription "to" in the
|
|
roster by sending <presence type='subscribed'/> stanza to user. This option
|
|
is only needed for JIT ICQ transport.
|
|
Warning: by enabling this option, ejabberd will not be fully XMPP compliant
|
|
anymore.
|
|
|
|
Documentation and Internationalization
|
|
|
|
- Documentation has been extended to cover more topics.
|
|
- Translations have been updated.
|
|
|
|
Bugfixes
|
|
|
|
- This release contains several bugfixes.
|
|
- Among other bugfixes include improvements to the client-to-server (c2s)
|
|
connection management module.
|
|
- Please refer to the ChangeLog file supplied
|
|
with this release regarding all improvements in ejabberd.
|
|
|
|
|
|
Installation Notes
|
|
|
|
|
|
Supported Erlang Version
|
|
|
|
- You need at least Erlang/OTP R9C to run ejabberd 1.0.0.
|
|
|
|
Installation
|
|
|
|
Installers are provided for Microsoft Windows and Linux/x86.
|
|
Installers can be retrieved from:
|
|
http://www.process-one.net/en/projects/ejabberd/download.html
|
|
|
|
Migration Notes
|
|
|
|
- Before any migration, ejabberd system and database must be properly
|
|
backed up.
|
|
- When upgrading an ODBC-based installation, you will need to change the
|
|
relational database schema. The following SQL commands must be run on the
|
|
database:
|
|
CREATE SEQUENCE spool_seq_seq;
|
|
ALTER TABLE spool ADD COLUMN seq integer;
|
|
ALTER TABLE spool ALTER COLUMN seq SET DEFAULT nextval('spool_seq_seq');
|
|
UPDATE spool SET seq = DEFAULT;
|
|
ALTER TABLE spool ALTER COLUMN seq SET NOT NULL;
|
|
|
|
References
|
|
|
|
Contributed tutorials of interest are:
|
|
- Migration from Jabberd1.4 to ejabberd:
|
|
http://ejabberd.jabber.ru/jabberd1-to-ejabberd
|
|
- Migration from Jabberd2 to ejabberd:
|
|
http://ejabberd.jabber.ru/jabberd2-to-ejabberd
|
|
- Transport configuration for connecting to other networks:
|
|
http://ejabberd.jabber.ru/tutorials-transports
|
|
|
|
END
|
|
|
|
</PRE>
|
|
<!--TOC subsection ejabberd 1.1.0-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc89">B.5</A> ejabberd 1.1.0</H3><!--SEC END -->
|
|
|
|
<PRE CLASS="verbatim">
|
|
Release Notes
|
|
ejabberd 1.1.0
|
|
24 April 2006
|
|
|
|
This document describes the main changes in ejabberd 1.1.0. This version
|
|
introduce new features including support for new Jabber Enhancement
|
|
Proposals and several performance improvements enabling deployments on an
|
|
even larger scale than already possible.
|
|
|
|
ejabberd can be downloaded from the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/
|
|
|
|
Detailed information can be found in the ejabberd Feature Sheet and User
|
|
Guide which are available on the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/docs.html
|
|
|
|
A complete list of changes is available from:
|
|
http://support.process-one.net/secure/ReleaseNote.jspa?projectId=10011&styleName=Html&version=10025
|
|
|
|
|
|
Recent changes include:
|
|
|
|
|
|
New Jabber Enhancement Proposal support:
|
|
|
|
- JEP-0050: Ad-Hoc Commands.
|
|
- JEP-0138: Stream Compression.
|
|
- JEP-0175: SASL anonymous.
|
|
|
|
Anonymous login
|
|
|
|
- SASL anonymous.
|
|
- Anonymous login for clients that do not yet support SASL Anonymous.
|
|
|
|
Relational database Support
|
|
|
|
- MySQL is now fully supported through ODBC and in native mode.
|
|
- Various improvements to the native database interfaces.
|
|
- The migration tool can use relational databases.
|
|
|
|
Multi-User Chat improvements
|
|
|
|
- Logging of room discussion to text file is now supported.
|
|
- Better reconfiguration support.
|
|
- Security oriented fixes.
|
|
- Several improvements and updates to latest JEP-0045.
|
|
|
|
Performance scalability improvements for large clusters
|
|
|
|
- Improved session synchronisation management between cluster nodes.
|
|
- Internal architecture has been reworked to use generalize Erlang/OTP
|
|
framework usage.
|
|
- Speed improvement on logger.
|
|
- TCP/IP packet reception change for better network throttling and
|
|
regulation.
|
|
As a result, these improvements will reduce load on large scale deployments.
|
|
|
|
XMPP Protocol related improvements
|
|
|
|
- XML stanza size can be limited.
|
|
- Messages are send to all resources with the same highest priority.
|
|
|
|
Documentation and Internationalization
|
|
|
|
- Documentation has been extended to cover more topics.
|
|
- Translations have been updated.
|
|
|
|
Web interface
|
|
|
|
- XHTML 1.0 compliance.
|
|
|
|
Bugfixes
|
|
|
|
- This release contains many bugfixes on various areas such as Publish-Subscribe, build
|
|
chain, installers, IRC gateway, ejabberdctl, amongst others.
|
|
- Please refer to the ChangeLog file supplied with this release regarding
|
|
all improvements in ejabberd.
|
|
|
|
|
|
|
|
Installation Notes
|
|
|
|
Supported Erlang Version
|
|
|
|
- You need at least Erlang/OTP R9C-2 to run ejabberd 1.1.0.
|
|
|
|
Installation
|
|
|
|
Installers are provided for Microsoft Windows, Linux/x86 and MacOSX/PPC.
|
|
Installers can be retrieved from:
|
|
http://www.process-one.net/en/projects/ejabberd/download.html
|
|
|
|
Migration Notes
|
|
|
|
- Before any migration, ejabberd system and database must be properly
|
|
backed up.
|
|
- The database schema has not been changed comparing to version 1.0.0 and
|
|
consequently it does not require any migration.
|
|
|
|
|
|
References
|
|
|
|
Contributed tutorials and documents of interest are:
|
|
- Migration from Jabberd1.4, Jabberd2 and WPJabber to ejabberd:
|
|
http://ejabberd.jabber.ru/migrate-to-ejabberd
|
|
- Transport configuration for connecting to other networks:
|
|
http://ejabberd.jabber.ru/tutorials-transports
|
|
- Using ejabberd with MySQL native driver:
|
|
http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver
|
|
- Anonymous User Support:
|
|
http://support.process-one.net/doc/display/MESSENGER/Anonymous+users+support
|
|
- Frequently Asked Questions:
|
|
http://ejabberd.jabber.ru/faq
|
|
|
|
END
|
|
</PRE>
|
|
<!--TOC subsection ejabberd 1.1.1-->
|
|
|
|
<H3 CLASS="subsection"><A NAME="htoc90">B.6</A> ejabberd 1.1.1</H3><!--SEC END -->
|
|
|
|
<PRE CLASS="verbatim">
|
|
Release Notes
|
|
ejabberd 1.1.1
|
|
28 April 2006
|
|
|
|
This document describes the main changes in ejabberd 1.1.x. This version
|
|
introduce new features including support for new Jabber Enhancement
|
|
Proposals and several performance improvements enabling deployments on an
|
|
even larger scale than already possible.
|
|
|
|
This release fix a security issue introduced in ejabberd 1.1.0. In SASL
|
|
mode, anonymous login was enabled as a default. Upgrading ejabberd 1.1.0 to
|
|
ejabberd 1.1.1 is highly recommended.
|
|
|
|
ejabberd can be downloaded from the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/
|
|
|
|
Detailed information can be found in the ejabberd Feature Sheet and User
|
|
Guide which are available on the Process-one website:
|
|
http://www.process-one.net/en/projects/ejabberd/docs.html
|
|
|
|
A complete list of changes is available from:
|
|
http://support.process-one.net/secure/ReleaseNote.jspa?projectId=10011&styleName=Html&version=10025
|
|
|
|
|
|
Recent changes include:
|
|
|
|
|
|
New Jabber Enhancement Proposal support:
|
|
|
|
- JEP-0050: Ad-Hoc Commands.
|
|
- JEP-0138: Stream Compression.
|
|
- JEP-0175: SASL anonymous.
|
|
|
|
Anonymous login
|
|
|
|
- SASL anonymous.
|
|
- Anonymous login for clients that do not yet support SASL Anonymous.
|
|
|
|
Relational database Support
|
|
|
|
- MySQL is now fully supported through ODBC and in native mode.
|
|
- Various improvements to the native database interfaces.
|
|
- The migration tool can use relational databases.
|
|
|
|
Multi-User Chat improvements
|
|
|
|
- Logging of room discussion to text file is now supported.
|
|
- Better reconfiguration support.
|
|
- Security oriented fixes.
|
|
- Several improvements and updates to latest JEP-0045.
|
|
|
|
Performance scalability improvements for large clusters
|
|
|
|
- Improved session synchronisation management between cluster nodes.
|
|
- Internal architecture has been reworked to use generalize Erlang/OTP
|
|
framework usage.
|
|
- Speed improvement on logger.
|
|
- TCP/IP packet reception change for better network throttling and
|
|
regulation.
|
|
As a result, these improvements will reduce load on large scale deployments.
|
|
|
|
XMPP Protocol related improvements
|
|
|
|
- XML stanza size can be limited.
|
|
- Messages are send to all resources with the same highest priority.
|
|
|
|
Documentation and Internationalization
|
|
|
|
- Documentation has been extended to cover more topics.
|
|
- Translations have been updated.
|
|
|
|
Web interface
|
|
|
|
- XHTML 1.0 compliance.
|
|
|
|
Bugfixes
|
|
|
|
- This release contains many bugfixes on various areas such as Publish-Subscribe, build
|
|
chain, installers, IRC gateway, ejabberdctl, amongst others.
|
|
- Please refer to the ChangeLog file supplied with this release regarding
|
|
all improvements in ejabberd.
|
|
|
|
|
|
|
|
Installation Notes
|
|
|
|
Supported Erlang Version
|
|
|
|
- You need at least Erlang/OTP R9C-2 to run ejabberd 1.1.0.
|
|
|
|
Installation
|
|
|
|
Installers are provided for Microsoft Windows, Linux/x86 and MacOSX/PPC.
|
|
Installers can be retrieved from:
|
|
http://www.process-one.net/en/projects/ejabberd/download.html
|
|
|
|
Migration Notes
|
|
|
|
- Before any migration, ejabberd system and database must be properly
|
|
backed up.
|
|
- The database schema has not been changed comparing to version 1.0.0 and
|
|
consequently it does not require any migration.
|
|
|
|
|
|
References
|
|
|
|
Contributed tutorials and documents of interest are:
|
|
- Migration from Jabberd1.4, Jabberd2 and WPJabber to ejabberd:
|
|
http://ejabberd.jabber.ru/migrate-to-ejabberd
|
|
- Transport configuration for connecting to other networks:
|
|
http://ejabberd.jabber.ru/tutorials-transports
|
|
- Using ejabberd with MySQL native driver:
|
|
http://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver
|
|
- Anonymous User Support:
|
|
http://support.process-one.net/doc/display/MESSENGER/Anonymous+users+support
|
|
- Frequently Asked Questions:
|
|
http://ejabberd.jabber.ru/faq
|
|
|
|
END
|
|
</PRE>
|
|
<!--TOC section Acknowledgements-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc91">C</A> <A NAME="acknowledgements">Acknowledgements</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:acknowledgements"></A>
|
|
Thanks to all people who contributed to this guide:
|
|
<UL CLASS="itemize"><LI CLASS="li-itemize">
|
|
Alexey Shchepin (<A HREF="xmpp:aleksey@jabber.ru"><TT>xmpp:aleksey@jabber.ru</TT></A>)
|
|
<LI CLASS="li-itemize">Badlop (<A HREF="xmpp:badlop@jabberes.org"><TT>xmpp:badlop@jabberes.org</TT></A>)
|
|
<LI CLASS="li-itemize">Evgeniy Khramtsov (<A HREF="xmpp:xram@jabber.ru"><TT>xmpp:xram@jabber.ru</TT></A>)
|
|
<LI CLASS="li-itemize">Florian Zumbiehl (<A HREF="xmpp:florz@florz.de"><TT>xmpp:florz@florz.de</TT></A>)
|
|
<LI CLASS="li-itemize">Michael Grigutsch (<A HREF="xmpp:migri@jabber.i-pobox.net"><TT>xmpp:migri@jabber.i-pobox.net</TT></A>)
|
|
<LI CLASS="li-itemize">Mickael Remond (<A HREF="xmpp:mremond@erlang-projects.org"><TT>xmpp:mremond@erlang-projects.org</TT></A>)
|
|
<LI CLASS="li-itemize">Sander Devrieze (<A HREF="xmpp:sander@devrieze.dyndns.org"><TT>xmpp:sander@devrieze.dyndns.org</TT></A>)
|
|
<LI CLASS="li-itemize">Sergei Golovan (<A HREF="xmpp:sgolovan@nes.ru"><TT>xmpp:sgolovan@nes.ru</TT></A>)
|
|
<LI CLASS="li-itemize">Vsevolod Pelipas (<A HREF="xmpp:vsevoload@jabber.ru"><TT>xmpp:vsevoload@jabber.ru</TT></A>)
|
|
</UL>
|
|
<!--TOC section Copyright Information-->
|
|
|
|
<H2 CLASS="section"><A NAME="htoc92">D</A> <A NAME="copyright">Copyright Information</A></H2><!--SEC END -->
|
|
|
|
<A NAME="sec:copyright"></A>
|
|
Ejabberd Installation and Operation Guide.<BR>
|
|
Copyright © January 23, 2003 — Alexey Shchepin<BR>
|
|
<BR>
|
|
This document is free software; you can redistribute it and/or
|
|
modify it under the terms of the GNU General Public License
|
|
as published by the Free Software Foundation; either version 2
|
|
of the License, or (at your option) any later version.<BR>
|
|
<BR>
|
|
This document is distributed in the hope that it will be useful,
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
GNU General Public License for more details.<BR>
|
|
<BR>
|
|
You should have received a copy of the GNU General Public License along with
|
|
this document; if not, write to the Free Software Foundation, Inc., 51 Franklin
|
|
Street, Fifth Floor, Boston, MA 02110-1301, USA.<BR>
|
|
<BR>
|
|
<!--HTMLFOOT-->
|
|
<!--ENDHTML-->
|
|
<!--FOOTER-->
|
|
<HR SIZE=2><BLOCKQUOTE CLASS="quote"><EM>This document was translated from L<sup>A</sup>T<sub>E</sub>X by
|
|
</EM><A HREF="http://pauillac.inria.fr/~maranget/hevea/index.html"><EM>H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A</EM></A><EM>.</EM></BLOCKQUOTE></BODY>
|
|
</HTML>
|