Chapril/xmpp.chapril.org-ejabberd
25
1
Fork 0
mirror of https://github.com/processone/ejabberd.git synced 2024-12-22 17:28:25 +01:00
Code Releases Activity
e5879f4349
xmpp.chapril.org-ejabberd/doc/guide.html
Mickaël Rémond 1b13449194 * doc/guide.tex: Documented the IQ discipline {queue, N}. 
* doc/guide.html: Likewise.

SVN Revision: 1278
2008-04-07 13:18:42 +00:00

4585 lines
210 KiB
HTML
Raw Blame History

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>
<TITLE>
ejabberd 2.1.0-alpha
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 -pedantic guide.tex -->
<!--HTMLHEAD-->
<!--ENDHTML-->
<!--PREFIX <ARG ></ARG>-->
<!--CUT DEF chapter 1 -->
<BR>
<BR>
<A NAME="titlepage"></A>
<TABLE CLASS="title">
<TR><TD>
<H1 CLASS="titlemain">
<HR SIZE=2><BR>
<BR>
<TABLE CELLSPACING=2 CELLPADDING=0>
<TR><TD ALIGN=right NOWRAP><FONT SIZE=6><B>ejabberd 2.1.0-alpha </B></FONT></TD>
</TR>
<TR><TD ALIGN=right NOWRAP>&nbsp;</TD>
</TR>
<TR><TD ALIGN=right NOWRAP><FONT SIZE=6>Installation and Operation Guide</FONT></TD>
</TR></TABLE><BR>
<BR>
<HR SIZE=2>
<BR><BR><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</H1>
<H3 CLASS="titlerest"><TABLE CELLSPACING=2 CELLPADDING=0>
<TR><TD VALIGN=top ALIGN=left>ejabberd Development Team</TD>
</TR></TABLE></H3>
<H3 CLASS="titlerest"></H3></TD>
</TR></TABLE><BR>
<!--TOC chapter Contents-->
<H1 CLASS="chapter">Contents</H1><!--SEC END -->
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc1">Chapter&nbsp;1&nbsp;&nbsp;Introduction</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc2">1.1&nbsp;&nbsp;Key Features</A>
<LI CLASS="li-toc"><A HREF="#htoc3">1.2&nbsp;&nbsp;Additional Features</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc4">Chapter&nbsp;2&nbsp;&nbsp;Installing <TT>ejabberd</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc5">2.1&nbsp;&nbsp;Installing <TT>ejabberd</TT> with Binary Installer</A>
<LI CLASS="li-toc"><A HREF="#htoc6">2.2&nbsp;&nbsp;Installing <TT>ejabberd</TT> with Operating System specific packages</A>
<LI CLASS="li-toc"><A HREF="#htoc7">2.3&nbsp;&nbsp;Installing <TT>ejabberd</TT> with CEAN</A>
<LI CLASS="li-toc"><A HREF="#htoc8">2.4&nbsp;&nbsp;Installing <TT>ejabberd</TT> from Source Code</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc9">2.4.1&nbsp;&nbsp;Requirements</A>
<LI CLASS="li-toc"><A HREF="#htoc10">2.4.2&nbsp;&nbsp;Download Source Code</A>
<LI CLASS="li-toc"><A HREF="#htoc11">2.4.3&nbsp;&nbsp;Compile</A>
<LI CLASS="li-toc"><A HREF="#htoc12">2.4.4&nbsp;&nbsp;Install</A>
<LI CLASS="li-toc"><A HREF="#htoc13">2.4.5&nbsp;&nbsp;Start</A>
<LI CLASS="li-toc"><A HREF="#htoc14">2.4.6&nbsp;&nbsp;Specific Notes for BSD</A>
<LI CLASS="li-toc"><A HREF="#htoc15">2.4.7&nbsp;&nbsp;Specific Notes for Microsoft Windows</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc16">2.5&nbsp;&nbsp;Create a Jabber Account for Administration</A>
<LI CLASS="li-toc"><A HREF="#htoc17">2.6&nbsp;&nbsp;Upgrading <TT>ejabberd</TT></A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc18">Chapter&nbsp;3&nbsp;&nbsp;Configuring <TT>ejabberd</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc19">3.1&nbsp;&nbsp;Basic Configuration</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc20">3.1.1&nbsp;&nbsp;Host Names</A>
<LI CLASS="li-toc"><A HREF="#htoc21">3.1.2&nbsp;&nbsp;Virtual Hosting</A>
<LI CLASS="li-toc"><A HREF="#htoc22">3.1.3&nbsp;&nbsp;Listening Ports</A>
<LI CLASS="li-toc"><A HREF="#htoc23">3.1.4&nbsp;&nbsp;Authentication</A>
<LI CLASS="li-toc"><A HREF="#htoc24">3.1.5&nbsp;&nbsp;Access Rules</A>
<LI CLASS="li-toc"><A HREF="#htoc25">3.1.6&nbsp;&nbsp;Shapers</A>
<LI CLASS="li-toc"><A HREF="#htoc26">3.1.7&nbsp;&nbsp;Default Language</A>
<LI CLASS="li-toc"><A HREF="#htoc27">3.1.8&nbsp;&nbsp;Include Additional Configuration Files</A>
<LI CLASS="li-toc"><A HREF="#htoc28">3.1.9&nbsp;&nbsp;Option Macros in Configuration File</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc29">3.2&nbsp;&nbsp;Database and LDAP Configuration</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc30">3.2.1&nbsp;&nbsp;MySQL</A>
<LI CLASS="li-toc"><A HREF="#htoc31">3.2.2&nbsp;&nbsp;Microsoft SQL Server</A>
<LI CLASS="li-toc"><A HREF="#htoc32">3.2.3&nbsp;&nbsp;PostgreSQL</A>
<LI CLASS="li-toc"><A HREF="#htoc33">3.2.4&nbsp;&nbsp;ODBC Compatible</A>
<LI CLASS="li-toc"><A HREF="#htoc34">3.2.5&nbsp;&nbsp;LDAP</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc35">3.3&nbsp;&nbsp;Modules Configuration</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc36">3.3.1&nbsp;&nbsp;Overview</A>
<LI CLASS="li-toc"><A HREF="#htoc37">3.3.2&nbsp;&nbsp;Common Options</A>
<LI CLASS="li-toc"><A HREF="#htoc38">3.3.3&nbsp;&nbsp;<TT>mod_announce</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc39">3.3.4&nbsp;&nbsp;<TT>mod_disco</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc40">3.3.5&nbsp;&nbsp;<TT>mod_echo</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc41">3.3.6&nbsp;&nbsp;<TT>mod_http_bind</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc42">3.3.7&nbsp;&nbsp;<TT>mod_http_fileserver</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc43">3.3.8&nbsp;&nbsp;<TT>mod_irc</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc44">3.3.9&nbsp;&nbsp;<TT>mod_last</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc45">3.3.10&nbsp;&nbsp;<TT>mod_muc</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc46">3.3.11&nbsp;&nbsp;<TT>mod_muc_log</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc47">3.3.12&nbsp;&nbsp;<TT>mod_offline</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc48">3.3.13&nbsp;&nbsp;<TT>mod_privacy</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc49">3.3.14&nbsp;&nbsp;<TT>mod_private</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc50">3.3.15&nbsp;&nbsp;<TT>mod_proxy65</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc51">3.3.16&nbsp;&nbsp;<TT>mod_pubsub</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc52">3.3.17&nbsp;&nbsp;<TT>mod_register</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc53">3.3.18&nbsp;&nbsp;<TT>mod_roster</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc54">3.3.19&nbsp;&nbsp;<TT>mod_service_log</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc55">3.3.20&nbsp;&nbsp;<TT>mod_shared_roster</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc56">3.3.21&nbsp;&nbsp;<TT>mod_stats</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc57">3.3.22&nbsp;&nbsp;<TT>mod_time</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc58">3.3.23&nbsp;&nbsp;<TT>mod_vcard</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc59">3.3.24&nbsp;&nbsp;<TT>mod_vcard_ldap</TT></A>
<LI CLASS="li-toc"><A HREF="#htoc60">3.3.25&nbsp;&nbsp;<TT>mod_version</TT></A>
</UL>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc61">Chapter&nbsp;4&nbsp;&nbsp;Managing an <TT>ejabberd</TT> server</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc62">4.1&nbsp;&nbsp;<TT>ejabberdctl</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc63">4.1.1&nbsp;&nbsp;Commands</A>
<LI CLASS="li-toc"><A HREF="#htoc64">4.1.2&nbsp;&nbsp;Erlang runtime system</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc65">4.2&nbsp;&nbsp;Web Admin</A>
<LI CLASS="li-toc"><A HREF="#htoc66">4.3&nbsp;&nbsp;Ad-hoc Commands</A>
<LI CLASS="li-toc"><A HREF="#htoc67">4.4&nbsp;&nbsp;Change Computer Hostname</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc68">Chapter&nbsp;5&nbsp;&nbsp;Securing <TT>ejabberd</TT></A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc69">5.1&nbsp;&nbsp;Firewall Settings</A>
<LI CLASS="li-toc"><A HREF="#htoc70">5.2&nbsp;&nbsp;epmd </A>
<LI CLASS="li-toc"><A HREF="#htoc71">5.3&nbsp;&nbsp;Erlang Cookie</A>
<LI CLASS="li-toc"><A HREF="#htoc72">5.4&nbsp;&nbsp;Erlang node name</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc73">Chapter&nbsp;6&nbsp;&nbsp;Clustering</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc74">6.1&nbsp;&nbsp;How it Works</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc75">6.1.1&nbsp;&nbsp;Router</A>
<LI CLASS="li-toc"><A HREF="#htoc76">6.1.2&nbsp;&nbsp;Local Router</A>
<LI CLASS="li-toc"><A HREF="#htoc77">6.1.3&nbsp;&nbsp;Session Manager</A>
<LI CLASS="li-toc"><A HREF="#htoc78">6.1.4&nbsp;&nbsp;s2s Manager</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc79">6.2&nbsp;&nbsp;Clustering Setup</A>
<LI CLASS="li-toc"><A HREF="#htoc80">6.3&nbsp;&nbsp;Service Load-Balancing</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc81">6.3.1&nbsp;&nbsp;Components Load-Balancing</A>
<LI CLASS="li-toc"><A HREF="#htoc82">6.3.2&nbsp;&nbsp;Domain Load-Balancing Algorithm</A>
<LI CLASS="li-toc"><A HREF="#htoc83">6.3.3&nbsp;&nbsp;Load-Balancing Buckets</A>
</UL>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc84">Chapter&nbsp;7&nbsp;&nbsp;Debugging</A>
<UL CLASS="toc"><LI CLASS="li-toc">
<A HREF="#htoc85">7.1&nbsp;&nbsp;Watchdog Alerts</A>
<LI CLASS="li-toc"><A HREF="#htoc86">7.2&nbsp;&nbsp;Log Files</A>
<LI CLASS="li-toc"><A HREF="#htoc87">7.3&nbsp;&nbsp;Debug Console</A>
</UL>
<LI CLASS="li-toc"><A HREF="#htoc88">Appendix&nbsp;A&nbsp;&nbsp;Internationalization and Localization</A>
<LI CLASS="li-toc"><A HREF="#htoc89">Appendix&nbsp;B&nbsp;&nbsp;Release Notes</A>
<LI CLASS="li-toc"><A HREF="#htoc90">Appendix&nbsp;C&nbsp;&nbsp;Acknowledgements</A>
<LI CLASS="li-toc"><A HREF="#htoc91">Appendix&nbsp;D&nbsp;&nbsp;Copyright Information</A>
</UL>
<!--TOC chapter Introduction-->
<H1 CLASS="chapter"><A NAME="htoc1">Chapter&nbsp;1</A>&nbsp;&nbsp;Introduction</H1><!--SEC END -->
<A NAME="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 section Key Features-->
<H2 CLASS="section"><A NAME="htoc2">1.1</A>&nbsp;&nbsp;Key Features</H2><!--SEC END -->
<A NAME="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. <LI CLASS="li-itemize">Web Administration.
<LI CLASS="li-itemize">Shared Roster Groups.
<LI CLASS="li-itemize">Command line administration tool. <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 to 24 languages. <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://www.ejabberd.im/protocols">Many protocols supported</A>.
</UL></UL>
<!--TOC section Additional Features-->
<H2 CLASS="section"><A NAME="htoc3">1.2</A>&nbsp;&nbsp;Additional Features</H2><!--SEC END -->
<A NAME="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 Admin accessible via HTTPS secure access.
</UL>
<LI CLASS="li-itemize">Databases
<UL CLASS="itemize"><LI CLASS="li-itemize">
Internal database for fast deployment (Mnesia).
<LI CLASS="li-itemize">Native MySQL support.
<LI CLASS="li-itemize">Native PostgreSQL support.
<LI CLASS="li-itemize">ODBC data storage support.
<LI CLASS="li-itemize">Microsoft SQL Server support. </UL>
<LI CLASS="li-itemize">Authentication
<UL CLASS="itemize"><LI CLASS="li-itemize">
Internal Authentication.
<LI CLASS="li-itemize">PAM, LDAP and ODBC. <LI CLASS="li-itemize">External Authentication script.
</UL>
<LI CLASS="li-itemize">Others
<UL CLASS="itemize"><LI CLASS="li-itemize">
Support for virtual hosting.
<LI CLASS="li-itemize">Compressing XML streams with Stream Compression (<A HREF="http://www.xmpp.org/extensions/xep-0138.html">XEP-0138</A>).
<LI CLASS="li-itemize">Statistics via Statistics Gathering (<A HREF="http://www.xmpp.org/extensions/xep-0039.html">XEP-0039</A>).
<LI CLASS="li-itemize">IPv6 support both for c2s and s2s connections.
<LI CLASS="li-itemize"><A HREF="http://www.xmpp.org/extensions/xep-0045.html">Multi-User Chat</A> module with support for clustering and HTML logging. <LI CLASS="li-itemize">Users Directory based on users vCards.
<LI CLASS="li-itemize"><A HREF="http://www.xmpp.org/extensions/xep-0060.html">Publish-Subscribe</A> component with support for <A HREF="http://www.xmpp.org/extensions/xep-00163.html">Personal Eventing via Pubsub</A>.
<LI CLASS="li-itemize">Support for web clients: <A HREF="http://www.xmpp.org/extensions/xep-0025.html">HTTP Polling</A> and <A HREF="http://www.xmpp.org/extensions/xep-0206.html">HTTP Binding (BOSH)</A> services.
<LI CLASS="li-itemize">IRC transport.
<LI CLASS="li-itemize">Component support: interface with networks such as AIM, ICQ and MSN installing special tranports.
</UL>
</UL>
<!--TOC chapter Installing <TT>ejabberd</TT>-->
<H1 CLASS="chapter"><A NAME="htoc4">Chapter&nbsp;2</A>&nbsp;&nbsp;Installing <TT>ejabberd</TT></H1><!--SEC END -->
<!--TOC section Installing <TT>ejabberd</TT> with Binary Installer-->
<H2 CLASS="section"><A NAME="htoc5">2.1</A>&nbsp;&nbsp;Installing <TT>ejabberd</TT> with Binary Installer</H2><!--SEC END -->
Probably the easiest way to install an <TT>ejabberd</TT> instant messaging server
is using the binary installer published by Process-one.
The binary installers of released <TT>ejabberd</TT> versions
are available in the Process-one <TT>ejabberd</TT> downloads page:
<A HREF="http://www.process-one.net/en/ejabberd/downloads"><TT>http://www.process-one.net/en/ejabberd/downloads</TT></A><BR>
<BR>
The installer will deploy and configure a full featured <TT>ejabberd</TT>
server and does not require any extra dependencies.<BR>
<BR>
In *nix systems, remember to set executable the binary installer before starting it. For example:
<PRE CLASS="verbatim">
chmod +x ejabberd-2.0.0_1-linux-x86-installer.bin
./ejabberd-2.0.0_1-linux-x86-installer.bin
</PRE>
<TT>ejabberd</TT> can be started manually at any time,
or automatically by the operating system at system boot time.<BR>
<BR>
To start and stop <TT>ejabberd</TT> manually,
use the desktop shortcuts created by the installer.
If the machine doesn't have a graphical system, use the scripts 'start'
and 'stop' in the 'bin' directory where <TT>ejabberd</TT> is installed.<BR>
<BR>
The Windows installer also adds ejabberd as a system service,
and a shortcut to a debug console for experienced administrators.
If you want ejabberd to be started automatically at boot time,
go to the Windows service settings and set ejabberd to be automatically started.
Note that the Windows service is a feature still in development,
and for example it doesn't read the file ejabberdctl.cfg.<BR>
<BR>
On a *nix system, if you want ejabberd to be started as daemon at boot time,
copy <TT>ejabberd.init</TT> from the 'bin' directory to something like <TT>/etc/init.d/ejabberd</TT>
(depending on your distribution) and call <TT>/etc/inid.d/ejabberd start</TT> to start it.<BR>
<BR>
The <TT>ejabberdctl</TT> administration script is included in the <TT>bin</TT> directory.
Please refer to the section&nbsp;<A HREF="#ejabberdctl">4.1</A> for details about <TT>ejabberdctl</TT>,
and configurable options to fine tune the Erlang runtime system.<BR>
<BR>
<!--TOC section Installing <TT>ejabberd</TT> with Operating System specific packages-->
<H2 CLASS="section"><A NAME="htoc6">2.2</A>&nbsp;&nbsp;Installing <TT>ejabberd</TT> with Operating System specific packages</H2><!--SEC END -->
Some Operating Systems provide a specific <TT>ejabberd</TT> package adapted to
the system architecture and libraries.
It usually also checks dependencies
and performs basic configuration tasks like creating the initial
administrator account. Some examples are Debian and Gentoo. Consult the
resources provided by your Operating System for more information.<BR>
<BR>
Usually those packages create a script like <TT>/etc/init.d/ejabberd</TT>
to start and stop <TT>ejabberd</TT> as a service at boot time.<BR>
<BR>
<!--TOC section Installing <TT>ejabberd</TT> with CEAN-->
<H2 CLASS="section"><A NAME="htoc7">2.3</A>&nbsp;&nbsp;Installing <TT>ejabberd</TT> with CEAN</H2><!--SEC END -->
<A HREF="http://cean.process-one.net/">CEAN</A>
(Comprehensive Erlang Archive Network) is a repository that hosts binary
packages from many Erlang programs, including <TT>ejabberd</TT> and all its dependencies.
The binaries are available for many different system architectures, so this is an
alternative to the binary installer and Operating System's <TT>ejabberd</TT> packages.<BR>
<BR>
You will have to create your own <TT>ejabberd</TT> start
script depending of how you handle your CEAN installation.
The default <TT>ejabberdctl</TT> script is located
into <TT>ejabberd</TT>'s priv directory and can be used as an example.<BR>
<BR>
<!--TOC section Installing <TT>ejabberd</TT> from Source Code-->
<H2 CLASS="section"><A NAME="htoc8">2.4</A>&nbsp;&nbsp;Installing <TT>ejabberd</TT> from Source Code</H2><!--SEC END -->
<A NAME="installation"></A>
The canonical form for distribution of <TT>ejabberd</TT> stable releases is the source code package.
Compiling <TT>ejabberd</TT> from source code is quite easy in *nix systems,
as long as your system have all the dependencies.<BR>
<BR>
<!--TOC subsection Requirements-->
<H3 CLASS="subsection"><A NAME="htoc9">2.4.1</A>&nbsp;&nbsp;Requirements</H3><!--SEC END -->
<A NAME="installreq"></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 R10B-9 up to R11B-5. Erlang R12 releases are not yet officially supported, and are not recommended for production servers.
<LI CLASS="li-itemize">OpenSSL 0.9.6 or higher, for STARTTLS, SASL and SSL encryption. Optional, highly recommended.
<LI CLASS="li-itemize">Zlib 1.2.3 or higher, for Stream Compression support (<A HREF="http://www.xmpp.org/extensions/xep-0138.html">XEP-0138</A>). Optional.
<LI CLASS="li-itemize">GNU Iconv 1.8 or higher, for the IRC Transport (mod_irc). Optional. Not needed on systems with GNU Libc.
</UL>
<!--TOC subsection Download Source Code-->
<H3 CLASS="subsection"><A NAME="htoc10">2.4.2</A>&nbsp;&nbsp;Download Source Code</H3><!--SEC END -->
<A NAME="download"></A>
Released versions of <TT>ejabberd</TT> are available in the Process-one <TT>ejabberd</TT> downloads page:
<A HREF="http://www.process-one.net/en/ejabberd/downloads"><TT>http://www.process-one.net/en/ejabberd/downloads</TT></A><BR>
<BR>
Alternatively, the latest development version can be retrieved from the Subversion repository using this command:
<PRE CLASS="verbatim">
svn co http://svn.process-one.net/ejabberd/trunk ejabberd
</PRE>
<!--TOC subsection Compile-->
<H3 CLASS="subsection"><A NAME="htoc11">2.4.3</A>&nbsp;&nbsp;Compile</H3><!--SEC END -->
<A NAME="compile"></A>
To compile <TT>ejabberd</TT> execute the commands:
<PRE CLASS="verbatim">
./configure
make
</PRE>
The build configuration script provides several parameters.
To get the full list run the command:
<PRE CLASS="verbatim">
./configure --help
</PRE>
Some options that you may be interested in modifying:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>&ndash;prefix=/</TT></B><DD CLASS="dd-description">
Specify the path prefix where the files will be copied when running the make install command.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>&ndash;enable-pam</TT></B><DD CLASS="dd-description">
Enable the PAM authentication method.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>&ndash;enable-odbc or &ndash;enable-mssql</TT></B><DD CLASS="dd-description">
Required if you want to use an external database.
See section&nbsp;<A HREF="#database">3.2</A> for more information.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>&ndash;enable-full-xml</TT></B><DD CLASS="dd-description">
Enable the use of XML based optimisations.
It will for example use CDATA to escape characters in the XMPP stream.
Use this option only if you are sure your Jabber clients include a fully compliant XML parser.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>&ndash;disable-transient-supervisors</TT></B><DD CLASS="dd-description">
Disable the use of Erlang/OTP supervision for transient processes.
</DL>
<!--TOC subsection Install-->
<H3 CLASS="subsection"><A NAME="htoc12">2.4.4</A>&nbsp;&nbsp;Install</H3><!--SEC END -->
<A NAME="install"></A>
To install <TT>ejabberd</TT> in the destination directories, run the command:
<PRE CLASS="verbatim">
make install
</PRE>Note that you may need to have administrative privileges in the system.<BR>
<BR>
The files and directories created are, by default:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>/etc/ejabberd/</TT></B><DD CLASS="dd-description"> Configuration files:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>ejabberd.cfg</TT></B><DD CLASS="dd-description"> ejabberd configuration file
<DT CLASS="dt-description"><B><TT>ejabberdctl.cfg</TT></B><DD CLASS="dd-description"> Configuration file of the administration script
<DT CLASS="dt-description"><B><TT>inetrc</TT></B><DD CLASS="dd-description"> Network DNS configuration
</DL>
<DT CLASS="dt-description"><B><TT>/sbin/ejabberdctl</TT></B><DD CLASS="dd-description"> Administration script
<DT CLASS="dt-description"><B><TT>/var/lib/ejabberd/</TT></B><DD CLASS="dd-description">
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>.erlang.cookie</TT></B><DD CLASS="dd-description"> Erlang cookie file
<DT CLASS="dt-description"><B><TT>db</TT></B><DD CLASS="dd-description"> Mnesia database spool files
<DT CLASS="dt-description"><B><TT>ebin</TT></B><DD CLASS="dd-description"> Binary Erlang files (*.beam)
<DT CLASS="dt-description"><B><TT>priv</TT></B><DD CLASS="dd-description">
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>lib</TT></B><DD CLASS="dd-description"> Binary system libraries (*.so)
<DT CLASS="dt-description"><B><TT>msgs</TT></B><DD CLASS="dd-description"> Translated strings (*.msgs)
</DL>
</DL>
<DT CLASS="dt-description"><B><TT>/var/log/ejabberd/</TT></B><DD CLASS="dd-description"> Log files (see section&nbsp;<A HREF="#logfiles">7.2</A>):
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>ejabberd.log</TT></B><DD CLASS="dd-description"> ejabberd service log
<DT CLASS="dt-description"><B><TT>sasl.log</TT></B><DD CLASS="dd-description"> Erlang/OTP system log
</DL>
</DL>
<!--TOC subsection Start-->
<H3 CLASS="subsection"><A NAME="htoc13">2.4.5</A>&nbsp;&nbsp;Start</H3><!--SEC END -->
<A NAME="start"></A>
You can use the <TT>ejabberdctl</TT> command line administration script to start and stop <TT>ejabberd</TT>.<BR>
<BR>
Usage example:
<PRE CLASS="verbatim">
$ ejabberdctl start
$ ejabberdctl status
Node ejabberd@localhost is started. Status: started
ejabberd is running
$ ejabberdctl stop
</PRE>Please refer to the section&nbsp;<A HREF="#ejabberdctl">4.1</A> for details about <TT>ejabberdctl</TT>,
and configurable options to fine tune the Erlang runtime system.<BR>
<BR>
<!--TOC subsection Specific Notes for BSD-->
<H3 CLASS="subsection"><A NAME="htoc14">2.4.6</A>&nbsp;&nbsp;Specific Notes for BSD</H3><!--SEC END -->
<A NAME="bsd"></A>
The command to compile <TT>ejabberd</TT> in BSD systems is:
<PRE CLASS="verbatim">
gmake
</PRE>
<!--TOC subsection Specific Notes for Microsoft Windows-->
<H3 CLASS="subsection"><A NAME="htoc15">2.4.7</A>&nbsp;&nbsp;Specific Notes for Microsoft Windows</H3><!--SEC END -->
<A NAME="windows"></A>
<!--TOC subsubsection Requirements-->
<H4 CLASS="subsubsection">Requirements</H4><!--SEC END -->
<A NAME="windowsreq"></A>
To compile <TT>ejabberd</TT> on a Microsoft Windows system, 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 R11B-5</A>
<LI CLASS="li-itemize"><A HREF="http://sourceforge.net/project/showfiles.php?group_id=10127&package_id=11277">Expat 2.0.0 or higher</A>
<LI CLASS="li-itemize"><A HREF="http://www.gnu.org/software/libiconv/">GNU Iconv 1.9.2</A>
(optional)
<LI CLASS="li-itemize"><A HREF="http://www.slproweb.com/products/Win32OpenSSL.html">Shining Light OpenSSL 0.9.8d or higher</A>
(to enable SSL connections)
<LI CLASS="li-itemize"><A HREF="http://www.zlib.net/">Zlib 1.2.3 or higher</A>
</UL>
<!--TOC subsubsection Compilation-->
<H4 CLASS="subsubsection">Compilation</H4><!--SEC END -->
<A NAME="windowscom"></A>
We assume that we will try to put as much library as possible into <CODE>C:\sdk\</CODE> to make it easier to track what is install for <TT>ejabberd</TT>.
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
Install Erlang emulator (for example, into <CODE>C:\sdk\erl5.5.5</CODE>).
<LI CLASS="li-enumerate">Install Expat library into <CODE>C:\sdk\Expat-2.0.0</CODE>
directory.<BR>
<BR>
Copy file <CODE>C:\sdk\Expat-2.0.0\Libs\libexpat.dll</CODE>
to your Windows system directory (for example, <CODE>C:\WINNT</CODE> or
<CODE>C:\WINNT\System32</CODE>)
<LI CLASS="li-enumerate">Build and install the Iconv library into the directory
<CODE>C:\sdk\GnuWin32</CODE>.<BR>
<BR>
Copy file <CODE>C:\sdk\GnuWin32\bin\lib*.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:\sdk\Expat-2.0.0\Libs</CODE> and
<CODE>C:\sdk\GnuWin32\bin</CODE> to the <CODE>PATH</CODE> environment
variable.
<LI CLASS="li-enumerate">Install OpenSSL in <CODE>C:\sdk\OpenSSL</CODE> and add <CODE>C:\sdk\OpenSSL\lib\VC</CODE> to your path or copy the binaries to your system directory.
<LI CLASS="li-enumerate">Install ZLib in <CODE>C:\sdk\gnuWin32</CODE>. Copy
<CODE>C:\sdk\GnuWin32\bin\zlib1.dll</CODE> to your system directory. If you change your path it should already be set after libiconv install.
<LI CLASS="li-enumerate">Make sure the you can access Erlang binaries from your path. For example: <CODE>set PATH=%PATH%;"C:\sdk\erl5.5.5\bin"</CODE>
<LI CLASS="li-enumerate">Depending on how you end up actually installing the library you might need to check and tweak the paths in the file configure.erl.
<LI CLASS="li-enumerate">While in the directory <CODE>ejabberd\src</CODE> run:
<PRE CLASS="verbatim">
configure.bat
nmake -f Makefile.win32
</PRE><LI CLASS="li-enumerate">Edit the file <CODE>ejabberd\src\ejabberd.cfg</CODE> and run
<PRE CLASS="verbatim">
werl -s ejabberd -name ejabberd
</PRE></OL>
<!--TOC section Create a Jabber Account for Administration-->
<H2 CLASS="section"><A NAME="htoc16">2.5</A>&nbsp;&nbsp;Create a Jabber Account for Administration</H2><!--SEC END -->
<A NAME="initialadmin"></A>
You need a Jabber account and grant him administrative privileges
to enter the <TT>ejabberd</TT> Web Admin:
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
Register a Jabber account on your <TT>ejabberd</TT> server, for example <TT>admin1@example.org</TT>.
There are two ways to register a Jabber account:
<OL CLASS="enumerate" type=a><LI CLASS="li-enumerate">
Using <TT>ejabberdctl</TT> (see section&nbsp;<A HREF="#ejabberdctl">4.1</A>):
<PRE CLASS="verbatim">
% ejabberdctl register admin1 example.org FgT5bk3
</PRE><LI CLASS="li-enumerate">Using a Jabber client and In-Band Registration (see section&nbsp;<A HREF="#modregister">3.3.17</A>).
</OL>
<LI CLASS="li-enumerate">Edit the <TT>ejabberd</TT> configuration file to give administration rights to the Jabber account you created:
<PRE CLASS="verbatim">
{acl, admins, {user, "admin1", "example.org"}}.
{access, configure, [{allow, admins}]}.
</PRE>You can grant administrative privileges to many Jabber accounts,
and also to accounts in other Jabber servers.
<LI CLASS="li-enumerate">Restart <TT>ejabberd</TT> to load the new configuration.
<LI CLASS="li-enumerate">Open the Web Admin (<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>admin1@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 Upgrading <TT>ejabberd</TT>-->
<H2 CLASS="section"><A NAME="htoc17">2.6</A>&nbsp;&nbsp;Upgrading <TT>ejabberd</TT></H2><!--SEC END -->
To upgrade an ejabberd installation to a new version,
simply uninstall the old version, and then install the new one.
Of course, it is important that the configuration file
and Mnesia database spool directory are not removed.<BR>
<BR>
<TT>ejabberd</TT> automatically updates the Mnesia table definitions at startup when needed.
If you also use an external database for storage of some modules,
check if the release notes of the new ejabberd version
indicates you need to also update those tables.<BR>
<BR>
<!--TOC chapter Configuring <TT>ejabberd</TT>-->
<H1 CLASS="chapter"><A NAME="htoc18">Chapter&nbsp;3</A>&nbsp;&nbsp;Configuring <TT>ejabberd</TT></H1><!--SEC END -->
<!--TOC section Basic Configuration-->
<H2 CLASS="section"><A NAME="htoc19">3.1</A>&nbsp;&nbsp;Basic Configuration</H2><!--SEC END -->
<A NAME="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 the internal <TT>ejabberd</TT> 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. <BR>
<BR>
Note that <TT>ejabberd</TT> never edits the configuration file.
So, the configuration changes done using the Web Admin
are stored in the database, but are not reflected in the configuration file.
If you want those changes to be use after <TT>ejabberd</TT> restart, you can either
edit the configuration file, or remove all its content.<BR>
<BR>
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 (shared between all <TT>ejabberd</TT> nodes in a
cluster), local options (which are specific for this particular <TT>ejabberd</TT> node)
and ACLs will be removed before new ones are added.<BR>
<BR>
<!--TOC subsection Host Names-->
<H3 CLASS="subsection"><A NAME="htoc20">3.1.1</A>&nbsp;&nbsp;Host Names</H3><!--SEC END -->
<A NAME="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="htoc21">3.1.2</A>&nbsp;&nbsp;Virtual Hosting</H3><!--SEC END -->
<A NAME="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, &lt;hostname&gt;, [&lt;option&gt;, &lt;option&gt;, ...]}.
</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_uids, [{"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_uids, [{"uid"}]},
{ldap_rootdn, "dc=localdomain"},
{ldap_rootdn, "dc=example,dc=com"},
{ldap_password, ""}]}.
</PRE></UL>
To define specific ejabberd modules in a virtual host,
you can define the global <TT>modules</TT> option with the common modules,
and later add specific modules to certain virtual hosts.
To accomplish that, instead of defining each option in <TT>host_config</TT> with the syntax
<PRE CLASS="verbatim">
{&lt;option-name&gt;, &lt;option-value&gt;}
</PRE>use this syntax:
<PRE CLASS="verbatim">
{{add, &lt;option-name&gt;}, &lt;option-value&gt;}
</PRE>
In this example three virtual hosts have some similar modules, but there are also
other different modules for some specific virtual hosts:
<PRE CLASS="verbatim">
% This ejabberd server has three vhosts:
{hosts, ["one.example.org", "two.example.org", "three.example.org"]}.
% Configuration of modules that are common to all vhosts
{modules,
[
{mod_roster, []},
{mod_configure, []},
{mod_disco, []},
{mod_private, []},
{mod_time, []},
{mod_last, []},
{mod_version, []}
]}.
% Add some modules to vhost one:
{host_config, "one.example.org", [{{add, modules}, [
{mod_echo, [{host, "echo-service.one.example.org"}]}
{mod_http_bind, []},
{mod_logxml, []}
]}]}.
% Add a module just to vhost two:
{host_config, "two.example.org", [{{add, modules}, [
{mod_echo, [{host, "mirror.two.example.org"}]}
]}]}.
</PRE>
<!--TOC subsection Listening Ports-->
<H3 CLASS="subsection"><A NAME="htoc22">3.1.3</A>&nbsp;&nbsp;Listening Ports</H3><!--SEC END -->
<A NAME="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>
The available modules, their purpose and the options allowed by each one are:
<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>&nbsp;</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>starttls</TT>, <TT>starttls_required</TT>, <TT>tls</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>&nbsp;</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
<A HREF="http://www.ejabberd.im/tutorials-transports">external components</A>
(as defined in the Jabber Component Protocol (<A HREF="http://www.xmpp.org/extensions/xep-0114.html">XEP-0114</A>).</TD>
</TR>
<TR><TD VALIGN=top ALIGN=left NOWRAP>&nbsp;</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>, <TT>service_check_from</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>&nbsp;</TD>
<TD VALIGN=top ALIGN=left NOWRAP>Options</TD>
<TD VALIGN=top ALIGN=left><TT>certfile</TT>, <TT>http_bind</TT>, <TT>http_poll</TT>,
<TT>inet6</TT>, <TT>ip</TT>, <TT>request_handlers</TT>, <TT>tls</TT>, <TT>web_admin</TT></TD>
</TR></TABLE>
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
This is a detailed description of each option allowed by the listening modules:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>{access, &lt;access rule&gt;}</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"> Full path to a file containing the default SSL certificate.
To define a certificate file specific for a given domain, use the global option <TT>domain_certfile</TT>.
<DT CLASS="dt-description"><B><TT>component_check_from</TT></B><DD CLASS="dd-description">
This option can be used with <TT>ejabberd_service</TT> only. It is
used to disable control on the from field on packets send by an
external components. The option can be either <TT>true</TT> or
<TT>false</TT>. The default value is <TT>true</TT> which conforms to <A HREF="http://www.xmpp.org/extensions/xep-0114.html">XEP-0114</A>.
<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_bind</TT></B><DD CLASS="dd-description">
This option enables HTTP Binding (<A HREF="http://www.xmpp.org/extensions/xep-0124.html">XEP-0124</A> and <A HREF="http://www.xmpp.org/extensions/xep-0206.html">XEP-0206</A>) support. HTTP Bind
enables access via HTTP requests to <TT>ejabberd</TT> from behind firewalls which
do not allow outgoing sockets on port 5222.<BR>
<BR>
Remember that you must also install and enable the module mod_http_bind.<BR>
<BR>
If HTTP Bind is enabled, it will be available at
<CODE>http://server:port/http-bind/</CODE>. Be aware that support for HTTP Bind
is also needed in the Jabber client. Remark also that HTTP Bind 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://www.ejabberd.im/jwchat">install JWChat</A> with
instructions for <TT>ejabberd</TT>).
<DT CLASS="dt-description"><B><TT>http_poll</TT></B><DD CLASS="dd-description">
This option enables HTTP Polling (<A HREF="http://www.xmpp.org/extensions/xep-0025.html">XEP-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://www.ejabberd.im/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>. Recommended values are 65536 for c2s
connections and 131072 for s2s connections. s2s max stanza size
must always much higher than c2s limit. Change this value with
extreme care as it can cause unwanted disconnect if set too low.
<DT CLASS="dt-description"><B><TT>{request_handlers, [{Path, Module}]}</TT></B><DD CLASS="dd-description"> To define one or several handlers that will serve HTTP requests.
The Path is a list of strings; so the URIs that start with that Path will be served by Module.
For example, if you want <TT>mod_foo</TT> to serve the URIs that start with <TT>/a/b/</TT>,
and you also want <TT>mod_http_bind</TT> to serve the URIs <TT>/http-bind/</TT>,
use this option: <TT>{request_handlers, [{["a", "b"], mod_foo}, {["http-bind"], mod_http_bind}]}</TT>
<DT CLASS="dt-description"><B><TT>{service_check_from, true|false}</TT></B><DD CLASS="dd-description">
By enabling this option, <TT>ejabberd</TT> allows the component to send packets with any arbitrary domain in the 'from' attribute.
Note that <A HREF="http://www.xmpp.org/extensions/xep-0114.html">XEP-0114</A> requires that the domain must match the hostname of the component.
Only enable this option if you are completely sure you need to enable it.
Default value: false.
<DT CLASS="dt-description"><B><TT>{shaper, &lt;access rule&gt;}</TT></B><DD CLASS="dd-description"> This option defines a
shaper for the port (see section&nbsp;<A HREF="#shapers">3.1.6</A>). The default value
is <TT>none</TT>.
<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.
You can define a certificate file for a specific domain using the global option <TT>domain_certfile</TT>.
<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.
You can define a certificate file for a specific domain using the global option <TT>domain_certfile</TT>.
<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>web_admin</TT></B><DD CLASS="dd-description"> This option
enables the Web Admin 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.
<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.xmpp.org/extensions/xep-0138.html">XEP-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).
</DL>
There are some additional global options:
<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"> Full path to a
file containing a SSL certificate.
<DT CLASS="dt-description"><B><TT>{domain_certfile, Domain, Path}</TT></B><DD CLASS="dd-description">
Full path to the file containing the SSL certificate for a specific domain.
<DT CLASS="dt-description"><B><TT>{s2s_default_policy, allow|deny}</TT></B><DD CLASS="dd-description">
The default policy for incoming and outgoing s2s connections to other Jabber servers.
The default value is <TT>allow</TT>.
<DT CLASS="dt-description"><B><TT>{{s2s_host, Host}, allow|deny}</TT></B><DD CLASS="dd-description">
Defines if incoming and outgoing s2s connections with a specific remote host are allowed or denied.
This allows to restrict ejabberd to only stablish s2s connections
with a small list of trusted servers, or to block some specific servers.
</DL>
For example, the following simple configuration defines:
<UL CLASS="itemize"><LI CLASS="li-itemize">
There are three domains. The default certificate file is <TT>server.pem</TT>.
However, the c2s and s2s connections to the domain <TT>example.com</TT> use the file <TT>example_com.pem</TT>.
<LI CLASS="li-itemize">Port 5222 listens for c2s connections with STARTTLS,
and also allows plain connections for old clients.
<LI CLASS="li-itemize">Port 5223 listens for c2s connections with the old SSL.
<LI CLASS="li-itemize">Port 5269 listens for s2s connections with STARTTLS.
<LI CLASS="li-itemize">Port 5280 listens for HTTP requests, and serves the HTTP Poll service.
<LI CLASS="li-itemize">Port 5281 listens for HTTP requests, and serves the Web Admin using HTTPS as explained in
section&nbsp;<A HREF="#webadmin">4.2</A>.
</UL>
<PRE CLASS="verbatim">
{hosts, ["example.com", "example.org", "example.net"]}.
{listen,
[
{5222, ejabberd_c2s, [
{access, c2s},
{shaper, c2s_shaper},
starttls, {certfile, "/etc/ejabberd/server.pem"},
{max_stanza_size, 65536}
]},
{5223, ejabberd_c2s, [
{access, c2s},
{shaper, c2s_shaper},
tls, {certfile, "/etc/ejabberd/server.pem"},
{max_stanza_size, 65536}
]},
{5269, ejabberd_s2s_in, [
{shaper, s2s_shaper},
{max_stanza_size, 131072}
]},
{5280, ejabberd_http, [
http_poll
]},
{5281, ejabberd_http, [
web_admin,
tls, {certfile, "/etc/ejabberd/server.pem"},
]}
]
}.
{s2s_use_starttls, true}.
{s2s_certfile, "/etc/ejabberd/server.pem"}.
{domain_certfile, "example.com", "/etc/ejabberd/example_com.pem"}.
</PRE>
In this example, 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.
Incoming and outgoing connections of remote Jabber servers are denied,
only two servers can connect: "jabber.example.org" and "example.com".
<LI CLASS="li-itemize">Port 5280 is serving the Web Admin and the HTTP Polling service. Note
that it is also possible to serve them on different ports. The second
example in section&nbsp;<A HREF="#webadmin">4.2</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&nbsp;Bytes/second
<LI CLASS="li-itemize">The
<A HREF="http://www.ejabberd.im/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://www.ejabberd.im/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://www.ejabberd.im/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://www.ejabberd.im/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://www.ejabberd.im/jmc">Jabber Mail Component</A>
<TT>jmc.example.org</TT> is connected to port 5238 with password
`<TT>jmcsecret</TT>'.
<LI CLASS="li-itemize">The service custom has enabled the special option to avoiding checking the <TT>from</TT> attribute in the packets send by this component. The component can send packets in behalf of any users from the server, or even on behalf of any server.
</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"}]}]},
{5239, ejabberd_service, [{host, "custom.example.org",
[{password, "customsecret"}]},
{service_check_from, false}]}
]
}.
{s2s_use_starttls, true}.
{s2s_certfile, "/path/to/ssl.pem"}.
{s2s_default_policy, deny}.
{{s2s_host,"jabber.example.org"}, allow}.
{{s2s_host,"example.com"}, allow}.
</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">
&lt;!--
You have to add elogger and rlogger entries here when using ejabberd.
In this case the transport will do the logging.
--&gt;
&lt;log id='logger'&gt;
&lt;host/&gt;
&lt;logtype/&gt;
&lt;format&gt;%d: [%t] (%h): %s&lt;/format&gt;
&lt;file&gt;/var/log/jabber/service.log&lt;/file&gt;
&lt;/log&gt;
&lt;!--
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.
--&gt;
&lt;xdb id="xdb"&gt;
&lt;host/&gt;
&lt;load&gt;
&lt;!-- this is a lib of wpjabber or jabberd --&gt;
&lt;xdb_file&gt;/usr/lib/jabber/xdb_file.so&lt;/xdb_file&gt;
&lt;/load&gt;
&lt;xdb_file xmlns="jabber:config:xdb_file"&gt;
&lt;spool&gt;&lt;jabberd:cmdline flag='s'&gt;/var/spool/jabber&lt;/jabberd:cmdline&gt;&lt;/spool&gt;
&lt;/xdb_file&gt;
&lt;/xdb&gt;
</PRE>
<!--TOC subsection Authentication-->
<H3 CLASS="subsection"><A NAME="htoc23">3.1.4</A>&nbsp;&nbsp;Authentication</H3><!--SEC END -->
<A NAME="auth"></A>
The option <TT>auth_method</TT> defines the authentication method that is used
for user authentication:
<PRE CLASS="verbatim">
{auth_method, [&lt;method&gt;]}.
</PRE>
The following authentication methods are supported by <TT>ejabberd</TT>:
<UL CLASS="itemize"><LI CLASS="li-itemize">
internal (default) &mdash; See section&nbsp;<A HREF="#internalauth">3.1.4</A>.
<LI CLASS="li-itemize">external &mdash; There are <A HREF="http://www.ejabberd.im/extauth">some
example authentication scripts</A>.
<LI CLASS="li-itemize">ldap &mdash; See section&nbsp;<A HREF="#ldap">3.2.5</A>.
<LI CLASS="li-itemize">odbc &mdash; See section&nbsp;<A HREF="#mysql">3.2.1</A>, <A HREF="#pgsql">3.2.3</A>,
<A HREF="#mssql">3.2.2</A> and <A HREF="#odbc">3.2.4</A>.
<LI CLASS="li-itemize">anonymous &mdash; See section&nbsp;<A HREF="#saslanonymous">3.1.4</A>.
<LI CLASS="li-itemize">pam &mdash; See section&nbsp;<A HREF="#pam">3.1.4</A>.
</UL>
<!--TOC subsubsection Internal-->
<H4 CLASS="subsubsection">Internal</H4><!--SEC END -->
<A NAME="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">SASL Anonymous and Anonymous Login</H4><!--SEC END -->
<A NAME="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&nbsp;<A HREF="#virtualhost">3.1.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&nbsp;<A HREF="#virtualhost">3.1.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, [internal,anonymous]},
{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, [internal,anonymous]},
{anonymous_protocol, both}]}.
</PRE></UL>
<!--TOC subsubsection PAM Authentication-->
<H4 CLASS="subsubsection">PAM Authentication</H4><!--SEC END -->
<A NAME="pam"></A>
<TT>ejabberd</TT> supports authentication via Pluggable Authentication Modules (PAM).
PAM is currently supported in AIX, FreeBSD, HP-UX, Linux, Mac OS X, NetBSD and Solaris.
PAM authentication is disabled by default, so you have to configure and compile
<TT>ejabberd</TT> with PAM support enabled:
<PRE CLASS="verbatim">
./configure --enable-pam &amp;&amp; make install
</PRE>
Options:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>pam_service</TT></B><DD CLASS="dd-description">This option defines the PAM service name.
Default is <TT>"ejabberd"</TT>. Refer to the PAM documentation of your operation system
for more information.
</DL>
Example:
<PRE CLASS="verbatim">
{auth_method, [pam]}.
{pam_service, "ejabberd"}.
</PRE>
Though it is quite easy to set up PAM support in <TT>ejabberd</TT>, PAM itself introduces some
security issues:
<UL CLASS="itemize"><LI CLASS="li-itemize">
To perform PAM authentication <TT>ejabberd</TT> uses external C-program called
<TT>epam</TT>. By default, it is located in <CODE>/var/lib/ejabberd/priv/lib/</CODE>
directory. You have to set it root on execution in the case when your PAM module
requires root privileges (<TT>pam_unix.so</TT> for example). Also you have to grant access
for <TT>ejabberd</TT> to this file and remove all other permissions from it:
<PRE CLASS="verbatim">
# chown root:ejabberd /var/lib/ejabberd/priv/bin/epam
# chmod 4750 /var/lib/ejabberd/priv/bin/epam
</PRE><LI CLASS="li-itemize">Make sure you have the latest version of PAM installed on your system.
Some old versions of PAM modules cause memory leaks. If you are not able to use the latest
version, you can <TT>kill(1)</TT> <TT>epam</TT> process periodically to reduce its memory
consumption: <TT>ejabberd</TT> will restart this process immediately.
<LI CLASS="li-itemize"><TT>epam</TT> program tries to turn off delays on authentication failures.
However, some PAM modules ignore this behavior and rely on their own configuration options.
The example configuration file <TT>ejabberd.pam</TT> shows how to turn off delays in
<TT>pam_unix.so</TT> module. It is not a ready to use configuration file: you must use it
as a hint when building your own PAM configuration instead. Note that if you want to disable
delays on authentication failures in the PAM configuration file, you have to restrict access
to this file, so a malicious user can't use your configuration to perform brute-force
attacks.
<LI CLASS="li-itemize">You may want to allow login access only for certain users. <TT>pam_listfile.so</TT>
module provides such functionality.
</UL>
<!--TOC subsection Access Rules-->
<H3 CLASS="subsection"><A NAME="htoc24">3.1.5</A>&nbsp;&nbsp;Access Rules</H3><!--SEC END -->
<A NAME="accessrules"></A>
<!--TOC subsubsection ACL Definition-->
<H4 CLASS="subsubsection">ACL Definition</H4><!--SEC END -->
<A NAME="ACLDefinition"></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, &lt;aclname&gt;, {&lt;acltype&gt;, ...}}.
</PRE><TT>&lt;acltype&gt;</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, &lt;username&gt;}</TT></B><DD CLASS="dd-description"> Matches the user with the name
<TT>&lt;username&gt;</TT> at the first virtual host. Example:
<PRE CLASS="verbatim">
{acl, admin, {user, "yozhik"}}.
</PRE><DT CLASS="dt-description"><B><TT>{user, &lt;username&gt;, &lt;server&gt;}</TT></B><DD CLASS="dd-description"> Matches the user with the JID
<TT>&lt;username&gt;@&lt;server&gt;</TT> and any resource. Example:
<PRE CLASS="verbatim">
{acl, admin, {user, "yozhik", "example.org"}}.
</PRE><DT CLASS="dt-description"><B><TT>{server, &lt;server&gt;}</TT></B><DD CLASS="dd-description"> Matches any JID from server
<TT>&lt;server&gt;</TT>. Example:
<PRE CLASS="verbatim">
{acl, exampleorg, {server, "example.org"}}.
</PRE><DT CLASS="dt-description"><B><TT>{user_regexp, &lt;regexp&gt;}</TT></B><DD CLASS="dd-description"> Matches any local user with a name that
matches <TT>&lt;regexp&gt;</TT> on local virtual hosts. Example:
<PRE CLASS="verbatim">
{acl, tests, {user_regexp, "^test[0-9]*$"}}.
</PRE><DT CLASS="dt-description"><B><TT>{user_regexp, &lt;regexp&gt;, &lt;server&gt;}</TT></B><DD CLASS="dd-description"> Matches any user with a name
that matches <TT>&lt;regexp&gt;</TT> at server <TT>&lt;server&gt;</TT>. Example:
<PRE CLASS="verbatim">
{acl, tests, {user_regexp, "^test", "example.org"}}.
</PRE><DT CLASS="dt-description"><B><TT>{server_regexp, &lt;regexp&gt;}</TT></B><DD CLASS="dd-description"> Matches any JID from the server that
matches <TT>&lt;regexp&gt;</TT>. Example:
<PRE CLASS="verbatim">
{acl, icq, {server_regexp, "^icq\\."}}.
</PRE><DT CLASS="dt-description"><B><TT>{node_regexp, &lt;user_regexp&gt;, &lt;server_regexp&gt;}</TT></B><DD CLASS="dd-description"> Matches any user
with a name that matches <TT>&lt;user_regexp&gt;</TT> at any server that matches
<TT>&lt;server_regexp&gt;</TT>. Example:
<PRE CLASS="verbatim">
{acl, yohzik, {node_regexp, "^yohzik$", "^example.(com|org)$"}}.
</PRE><DT CLASS="dt-description"><B><TT>{user_glob, &lt;glob&gt;}</TT></B><DD CLASS="dd-description">
<DT CLASS="dt-description"><B><TT>{user_glob, &lt;glob&gt;, &lt;server&gt;}</TT></B><DD CLASS="dd-description">
<DT CLASS="dt-description"><B><TT>{server_glob, &lt;glob&gt;}</TT></B><DD CLASS="dd-description">
<DT CLASS="dt-description"><B><TT>{node_glob, &lt;user_glob&gt;, &lt;server_glob&gt;}</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>
<!--TOC subsubsection Access Rights-->
<H4 CLASS="subsubsection">Access Rights</H4><!--SEC END -->
<A NAME="AccessRights"></A>
An entry allowing or denying access to different services looks similar to
this:
<PRE CLASS="verbatim">
{access, &lt;accessname&gt;, [{allow, &lt;aclname&gt;},
{deny, &lt;aclname&gt;},
...
]}.
</PRE>When a JID is checked to have access to <TT>&lt;accessname&gt;</TT>, the server
sequentially checks if that JID matches 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 subsubsection Limiting Opened Sessions with ACL-->
<H4 CLASS="subsubsection">Limiting Opened Sessions with ACL</H4><!--SEC END -->
<A NAME="configmaxsessions"></A>
The special access <TT>max_user_sessions</TT> 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>infinity</TT>.<BR>
<BR>
The syntax is:
<PRE CLASS="verbatim">
{access, max_user_sessions, [{&lt;maxnumber&gt;, &lt;aclname&gt;},
...
]}.
</PRE>
Examples:
<UL CLASS="itemize"><LI CLASS="li-itemize">
To limit the number of sessions per user to 10 for all users:
<PRE CLASS="verbatim">
{access, max_user_sessions, [{10, all}]}.
</PRE></UL>
<!--TOC subsection Shapers-->
<H3 CLASS="subsection"><A NAME="htoc25">3.1.6</A>&nbsp;&nbsp;Shapers</H3><!--SEC END -->
<A NAME="shapers"></A>
Shapers enable you to limit connection traffic. The syntax of
shapers is like this:
<PRE CLASS="verbatim">
{shaper, &lt;shapername&gt;, &lt;kind&gt;}.
</PRE>Currently only one kind of shaper called <TT>maxrate</TT> is available. It has the
following syntax:
<PRE CLASS="verbatim">
{maxrate, &lt;rate&gt;}
</PRE>where <TT>&lt;rate&gt;</TT> stands for the maximum allowed incoming rate in bytes per
second.
When a connection exceeds this limit, <TT>ejabberd</TT> stops reading from the socket
until the average rate is again below the allowed maximum.<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&nbsp;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&nbsp;bytes/second:
<PRE CLASS="verbatim">
{shaper, fast, {maxrate, 50000}}.
</PRE></UL>
<!--TOC subsection Default Language-->
<H3 CLASS="subsection"><A NAME="htoc26">3.1.7</A>&nbsp;&nbsp;Default Language</H3><!--SEC END -->
<A NAME="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>&lt;language&gt;.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 subsection Include Additional Configuration Files-->
<H3 CLASS="subsection"><A NAME="htoc27">3.1.8</A>&nbsp;&nbsp;Include Additional Configuration Files</H3><!--SEC END -->
<A NAME="includeconfigfile"></A>
The option <TT>include_config_file</TT> in a configuration file instructs <TT>ejabberd</TT> to include other configuration files immediately.<BR>
<BR>
The basic usage is:
<PRE CLASS="verbatim">
{include_config_file, &lt;filename&gt;}.
</PRE>It is also possible to specify suboptions:
<PRE CLASS="verbatim">
{include_config_file, &lt;filename&gt;, [&lt;suboption&gt;, &lt;suboption&gt;, ...]}.
</PRE>
The filename can be indicated either as an absolute path,
or relative to the main <TT>ejabberd</TT> configuration file.
It isn't possible to use wildcards.
The file must exist and be readable.<BR>
<BR>
The allowed suboptions are:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>{disallow, [&lt;option&gt;, &lt;option&gt;, ...]}</TT></B><DD CLASS="dd-description"> Disallows the usage of those options in the included configuration file.
The options that match this criteria are not accepted.
The default value is an empty list: <TT>[]</TT>
<DT CLASS="dt-description"><B><TT>{allow_only, [&lt;option&gt;, &lt;option&gt;, ...]}</TT></B><DD CLASS="dd-description"> Allows only the usage of those options in the included configuration file.
The options that do not match this criteria are not accepted.
The default value is: <TT>all</TT>
</DL>
This is a basic example:
<PRE CLASS="verbatim">
{include_config_file, "/etc/ejabberd/additional.cfg"}.
</PRE>
In this example, the included file is not allowed to contain a <TT>listen</TT> option.
If such an option is present, the option will not be accepted.
The file is in a subdirectory from where the main configuration file is.
<PRE CLASS="verbatim">
{include_config_file, "./example.org/additional_not_listen.cfg", [{disallow, [listen]}]}.
</PRE>
In this example, <TT>ejabberd.cfg</TT> defines some ACL and Access rules,
and later includes another file with additional rules:
<PRE CLASS="verbatim">
{acl, admin, {user, "admin", "localhost"}}.
{access, announce, [{allow, admin}]}.
{include_config_file, "/etc/ejabberd/acl_and_access.cfg", [{allow_only, [acl, access]}]}.
</PRE>and content of the file <TT>acl_and_access.cfg</TT> can be, for example:
<PRE CLASS="verbatim">
{acl, admin, {user, "bob", "localhost"}}.
{acl, admin, {user, "jan", "localhost"}}.
</PRE>
<!--TOC subsection Option Macros in Configuration File-->
<H3 CLASS="subsection"><A NAME="htoc28">3.1.9</A>&nbsp;&nbsp;Option Macros in Configuration File</H3><!--SEC END -->
<A NAME="optionmacros"></A>
In the <TT>ejabberd</TT> configuration file,
it is possible to define a macro for a value
and later use this macro when defining an option.<BR>
<BR>
A macro is defined with this syntax:
<PRE CLASS="verbatim">
{define_macro, '&lt;MACRO&gt;', &lt;value&gt;}.
</PRE>The <TT>MACRO</TT> must be surrounded by commas, and all in uppercase.
The <TT>value</TT> can be any valid arbitrary Erlang term.<BR>
<BR>
The first definition of a macro is preserved,
and additional definitions of the same macro are forgotten.<BR>
<BR>
Macros are processed after
additional configuration files have been included,
so it is possible to use macros that
are defined in configuration files included before the usage.<BR>
<BR>
It isn't possible to use a macro in the definition
of another macro.<BR>
<BR>
There are two ways to use a macro:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description"><B><TT>'&lt;MACRO&gt;'</TT></B><DD CLASS="dd-description">
You can put this instead of a value in an <TT>ejabberd</TT> option,
and will be replaced with the <TT>value</TT> previously defined.
If the macro is not defined previously,
the program will crash and report an error.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>{use_macro, '&lt;MACRO&gt;', &lt;defaultvalue&gt;}</TT></B><DD CLASS="dd-description">
Use a macro even if it may not be defined.
If the macro is not defined previously,
the provided <TT>defaultvalue</TT> is used.
This usage behaves as if it were defined and used this way:
<PRE CLASS="verbatim">
{define_macro, '&lt;MACRO&gt;', &lt;defaultvalue&gt;}.
'&lt;MACRO&gt;'
</PRE></DL>
This example shows the basic usage of a macro:
<PRE CLASS="verbatim">
{define_macro, 'LOG_LEVEL_NUMBER', 5}.
{loglevel, 'LOG_LEVEL_NUMBER'}.
</PRE>The resulting option interpreted by <TT>ejabberd</TT> is: <TT>{loglevel, 5}</TT>.<BR>
<BR>
This example shows that values can be any arbitrary Erlang term:
<PRE CLASS="verbatim">
{define_macro, 'USERBOB', {user, "bob", "localhost"}}.
{acl, admin, 'USERBOB'}.
</PRE>The resulting option interpreted by <TT>ejabberd</TT> is: <TT>{acl, admin, {user, "bob", "localhost"}}</TT>.<BR>
<BR>
This complex example:
<PRE CLASS="verbatim">
{define_macro, 'NUMBER_PORT_C2S', 5222}.
{define_macro, 'PORT_S2S_IN', {5269, ejabberd_s2s_in, []}}.
{listen,
[
{'NUMBER_PORT_C2S', ejabberd_c2s, []},
'PORT_S2S_IN',
{{use_macro, 'NUMBER_PORT_HTTP', 5280}, ejabberd_http, []}
]
}.
</PRE>produces this result after being interpreted:
<PRE CLASS="verbatim">
{listen,
[
{5222, ejabberd_c2s, []},
{5269, ejabberd_s2s_in, []},
{5280, ejabberd_http, []}
]
}.
</PRE>
<!--TOC section Database and LDAP Configuration-->
<H2 CLASS="section"><A NAME="htoc29">3.2</A>&nbsp;&nbsp;Database and LDAP Configuration</H2><!--SEC END -->
<A NAME="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 persistent,
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&nbsp;<A HREF="#ad">3.2.5</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="htoc30">3.2.1</A>&nbsp;&nbsp;MySQL</H3><!--SEC END -->
<A NAME="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 <TT>ejabberd</TT> schema for MySQL. At the end of the file
you can find information to update your database schema.<BR>
<BR>
By default <TT>ejabberd</TT> opens 10 connections to the database for each virtual host.
Use this option to modify the value:
<PRE CLASS="verbatim">
{odbc_pool_size, 10}.
</PRE>
You can configure an interval to make a dummy SQL request
to keep alive the connections to the database.
The default value is 'undefined', so no keepalive requests are made.
Specify in seconds: for example 28800 means 8 hours.
<PRE CLASS="verbatim">
{odbc_keepalive_interval, undefined}.
</PRE>
<!--TOC subsubsection Driver Compilation-->
<H4 CLASS="subsubsection">Driver Compilation</H4><!--SEC END -->
<A NAME="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 <TT>ejabberd</TT> .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 &amp;&amp; make install
</PRE></OL>
<!--TOC subsubsection Authentication-->
<H4 CLASS="subsubsection">Authentication</H4><!--SEC END -->
<A NAME="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>
Optionally, it is possible to define the MySQL port to use. This
option is only useful, in very rare cases, when you are not running
MySQL with the default port setting. The <TT>mysql</TT> parameter
can thus take the following form:
<PRE CLASS="verbatim">
{mysql, "Server", Port, "Database", "Username", "Password"}
</PRE>
The <TT>Port</TT> value should be an integer, without quotes. For example:
<PRE CLASS="verbatim">
{odbc_server, {mysql, "localhost", Port, "test", "root", "password"}}.
</PRE>
<!--TOC subsubsection Storage-->
<H4 CLASS="subsubsection">Storage</H4><!--SEC END -->
<A NAME="mysqlstorage"></A>
MySQL also can be used to store information into from several <TT>ejabberd</TT>
modules. See section&nbsp;<A HREF="#modoverview">3.3.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="htoc31">3.2.2</A>&nbsp;&nbsp;Microsoft SQL Server</H3><!--SEC END -->
<A NAME="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 <TT>ejabberd</TT> schema for Microsoft SQL Server. At the end
of the file you can find information to update your database schema.<BR>
<BR>
By default <TT>ejabberd</TT> opens 10 connections to the database for each virtual host.
Use this option to modify the value:
<PRE CLASS="verbatim">
{odbc_pool_size, 10}.
</PRE>
You can configure an interval to make a dummy SQL request
to keep alive the connections to the database.
The default value is 'undefined', so no keepalive requests are made.
Specify in seconds: for example 28800 means 8 hours.
<PRE CLASS="verbatim">
{odbc_keepalive_interval, undefined}.
</PRE>
<!--TOC subsubsection Driver Compilation-->
<H4 CLASS="subsubsection">Driver Compilation</H4><!--SEC END -->
<A NAME="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 &amp;&amp; make install
</PRE>
<!--TOC subsubsection Authentication-->
<H4 CLASS="subsubsection">Authentication</H4><!--SEC END -->
<A NAME="mssqlauth"></A>
The configuration of Microsoft SQL Server is the same as the configuration of
ODBC compatible servers (see section&nbsp;<A HREF="#odbcauth">3.2.4</A>).<BR>
<BR>
<!--TOC subsubsection Storage-->
<H4 CLASS="subsubsection">Storage</H4><!--SEC END -->
<A NAME="mssqlstorage"></A>
Microsoft SQL Server also can be used to store information into from several
<TT>ejabberd</TT> modules. See section&nbsp;<A HREF="#modoverview">3.3.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="htoc32">3.2.3</A>&nbsp;&nbsp;PostgreSQL</H3><!--SEC END -->
<A NAME="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 <TT>ejabberd</TT> schema for PostgreSQL. At the end of the file
you can find information to update your database schema.<BR>
<BR>
By default <TT>ejabberd</TT> opens 10 connections to the database for each virtual host.
Use this option to modify the value:
<PRE CLASS="verbatim">
{odbc_pool_size, 10}.
</PRE>
You can configure an interval to make a dummy SQL request
to keep alive the connections to the database.
The default value is 'undefined', so no keepalive requests are made.
Specify in seconds: for example 28800 means 8 hours.
<PRE CLASS="verbatim">
{odbc_keepalive_interval, undefined}.
</PRE>
<!--TOC subsubsection Driver Compilation-->
<H4 CLASS="subsubsection">Driver Compilation</H4><!--SEC END -->
<A NAME="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://www.ejabberd.im/ejabberd-modules/">ejabberd-modules SVN repository</A>.
Make sure the compiled
files are in your Erlang path; you can put them for example in the same
directory as your <TT>ejabberd</TT> .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 &amp;&amp; make install
</PRE></OL>
<!--TOC subsubsection Authentication-->
<H4 CLASS="subsubsection">Authentication</H4><!--SEC END -->
<A NAME="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>
Optionally, it is possible to define the PostgreSQL port to use. This
option is only useful, in very rare cases, when you are not running
PostgreSQL with the default port setting. The <TT>pgsql</TT> parameter
can thus take the following form:
<PRE CLASS="verbatim">
{pgsql, "Server", Port, "Database", "Username", "Password"}
</PRE>
The <TT>Port</TT> value should be an integer, without quotes. For example:
<PRE CLASS="verbatim">
{odbc_server, {pgsql, "localhost", 5432, "database", "ejabberd", "password"}}.
</PRE>
<!--TOC subsubsection Storage-->
<H4 CLASS="subsubsection">Storage</H4><!--SEC END -->
<A NAME="pgsqlstorage"></A>
PostgreSQL also can be used to store information into from several <TT>ejabberd</TT>
modules. See section&nbsp;<A HREF="#modoverview">3.3.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="htoc33">3.2.4</A>&nbsp;&nbsp;ODBC Compatible</H3><!--SEC END -->
<A NAME="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>
By default <TT>ejabberd</TT> opens 10 connections to the database for each virtual host.
Use this option to modify the value:
<PRE CLASS="verbatim">
{odbc_pool_size, 10}.
</PRE>
You can configure an interval to make a dummy SQL request
to keep alive the connections to the database.
The default value is 'undefined', so no keepalive requests are made.
Specify in seconds: for example 28800 means 8 hours.
<PRE CLASS="verbatim">
{odbc_keepalive_interval, undefined}.
</PRE>
<!--TOC subsubsection Driver Compilation-->
<H4 CLASS="subsubsection">Driver Compilation</H4><!--SEC END -->
<A NAME="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 <TT>ejabberd</TT> .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 &amp;&amp; make install
</PRE></OL>
<!--TOC subsubsection Authentication-->
<H4 CLASS="subsubsection">Authentication</H4><!--SEC END -->
<A NAME="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">Storage</H4><!--SEC END -->
<A NAME="odbcstorage"></A>
An ODBC compatible database also can be used to store information into from
several <TT>ejabberd</TT> modules. See section&nbsp;<A HREF="#modoverview">3.3.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="htoc34">3.2.5</A>&nbsp;&nbsp;LDAP</H3><!--SEC END -->
<A NAME="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">Connection</H4><!--SEC END -->
<A NAME="ldapconnection"></A>
Parameters:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>ldap_servers</TT></B><DD CLASS="dd-description"> List of IP addresses or DNS names of your
LDAP servers. 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 initial default value is&nbsp;389, so it is used when nothing is set into the
configuration file.
If you configure a value, it is stored in <TT>ejabberd</TT>'s database.
Then, if you remove that value from the configuration file,
the value previously stored in the database will be used instead of the default 389.
<DT CLASS="dt-description"><B><TT>ldap_rootdn</TT></B><DD CLASS="dd-description"> Bind DN. The default value
is&nbsp;<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">Authentication</H4><!--SEC END -->
<A NAME="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_uids</TT></B><DD CLASS="dd-description">LDAP attribute which holds a list
of attributes to use as alternatives for getting the JID. The value is of
the form: <TT>[{ldap_uidattr}]</TT> or <TT>[{ldap_uidattr,
ldap_uidattr_format}]</TT>. You can use as many comma separated tuples
<TT>{ldap_uidattr, ldap_uidattr_format}</TT> that is needed. The default
value is <TT>[{"uid", "%u"}]</TT>. The defaut <TT>ldap_uidattr_format</TT>
is <TT>"%u"</TT>. The values for <TT>ldap_uidattr</TT> and
<TT>ldap_uidattr_format</TT> are described as follow:
<DL CLASS="description" COMPACT=compact><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>.
</DL>
<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>"(&amp;(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">Examples</H4><!--SEC END -->
<A NAME="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> &mdash; email address, <TT>"givenName"</TT>
&mdash; first name, <TT>"sn"</TT> &mdash; second name, <TT>"birthDay"</TT> &mdash; 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"},
%% uidattr: user's part of JID is located in the "mail" attribute
%% uidattr_format: common format for our emails
{ldap_uids, [{"mail", "%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">Active Directory</H5><!--SEC END -->
<A NAME="ad"></A>
Active Directory is just an LDAP-server with predefined attributes. A sample
configuration is shown 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_uids, [{"sAMAccountName"}]}.
{ldap_filter, "(memberOf=*)"}.
{modules,
...
{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="htoc35">3.3</A>&nbsp;&nbsp;Modules Configuration</H2><!--SEC END -->
<A NAME="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="htoc36">3.3.1</A>&nbsp;&nbsp;Overview</H3><!--SEC END -->
<A NAME="modoverview"></A>
The following table lists all modules included in <TT>ejabberd</TT>.
<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.xmpp.org/extensions/xep-0050.html">XEP-0050</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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>recommends <TT>mod_adhoc</TT></TD>
<TD ALIGN=left NOWRAP>No</TD>
</TR>
<TR><TD ALIGN=left NOWRAP><TT>mod_caps</TT></TD>
<TD ALIGN=left NOWRAP>Request and cache Entity Capabilities (<A HREF="http://www.xmpp.org/extensions/xep-0115.html">XEP-0115</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</TD>
<TD ALIGN=left NOWRAP>No</TD>
</TR>
<TR><TD ALIGN=left NOWRAP><TT>mod_configure</TT></TD>
<TD ALIGN=left NOWRAP>Server configuration using Ad-Hoc</TD>
<TD ALIGN=left NOWRAP><TT>mod_adhoc</TT></TD>
<TD ALIGN=left NOWRAP>No</TD>
</TR>
<TR><TD ALIGN=left NOWRAP><TT>mod_disco</TT></TD>
<TD ALIGN=left NOWRAP>Service Discovery (<A HREF="http://www.xmpp.org/extensions/xep-0030.html">XEP-0030</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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>&nbsp;</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>&nbsp;</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.xmpp.org/extensions/xep-0012.html">XEP-0012</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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.xmpp.org/extensions/xep-0012.html">XEP-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.xmpp.org/extensions/xep-0045.html">XEP-0045</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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>&nbsp;</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 Communications</TD>
<TD ALIGN=left NOWRAP>&nbsp;</TD>
<TD ALIGN=left NOWRAP>Yes</TD>
</TR>
<TR><TD ALIGN=left NOWRAP><TT>mod_privacy_odbc</TT></TD>
<TD ALIGN=left NOWRAP>Blocking Communications</TD>
<TD ALIGN=left NOWRAP>supported database (*)</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.xmpp.org/extensions/xep-0049.html">XEP-0049</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</TD>
<TD ALIGN=left NOWRAP>No</TD>
</TR>
<TR><TD ALIGN=left NOWRAP><TT>mod_private_odbc</TT></TD>
<TD ALIGN=left NOWRAP>Private XML Storage (<A HREF="http://www.xmpp.org/extensions/xep-0049.html">XEP-0049</A>)</TD>
<TD ALIGN=left NOWRAP>supported database (*)</TD>
<TD ALIGN=left NOWRAP>No</TD>
</TR>
<TR><TD ALIGN=left NOWRAP><TT>mod_proxy65</TT></TD>
<TD ALIGN=left NOWRAP>SOCKS5 Bytestreams (<A HREF="http://www.xmpp.org/extensions/xep-0065.html">XEP-0065</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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.xmpp.org/extensions/xep-0060.html">XEP-0060</A>) and PEP (<A HREF="http://www.xmpp.org/extensions/xep-0163.html">XEP-0163</A>)</TD>
<TD ALIGN=left NOWRAP><TT>mod_caps</TT></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.xmpp.org/extensions/xep-0077.html">XEP-0077</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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>&nbsp;</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>&nbsp;</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>&nbsp;</TD>
<TD ALIGN=left NOWRAP>&nbsp;</TD>
<TD ALIGN=left NOWRAP><TT>mod_roster_odbc</TT></TD>
<TD ALIGN=left NOWRAP>&nbsp;</TD>
</TR>
<TR><TD ALIGN=left NOWRAP><TT>mod_stats</TT></TD>
<TD ALIGN=left NOWRAP>Statistics Gathering (<A HREF="http://www.xmpp.org/extensions/xep-0039.html">XEP-0039</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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.xmpp.org/extensions/xep-0090.html">XEP-0090</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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.xmpp.org/extensions/xep-0054.html">XEP-0054</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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.xmpp.org/extensions/xep-0054.html">XEP-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.xmpp.org/extensions/xep-0054.html">XEP-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.xmpp.org/extensions/xep-0092.html">XEP-0092</A>)</TD>
<TD ALIGN=left NOWRAP>&nbsp;</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&nbsp;<A HREF="#database">3.2</A>.
<LI CLASS="li-itemize">(**) This module or a similar one with another database backend is needed for
XMPP compliancy.
</UL>
You can see which database backend each module needs by looking at the suffix:
<UL CLASS="itemize"><LI CLASS="li-itemize">
No suffix, this means that the modules uses Erlang's built-in database
Mnesia as backend.
<LI CLASS="li-itemize">`_odbc', this means that the module needs a supported database
(see&nbsp;<A HREF="#database">3.2</A>) as backend.
<LI CLASS="li-itemize">`_ldap', this means that the module needs an LDAP server 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>.
<LI CLASS="li-itemize">Private XML storage: Use <TT>mod_private_odbc</TT> instead of <TT>mod_private</TT>.
<LI CLASS="li-itemize">User rules for blocking communications: Use <TT>mod_privacy_odbc</TT> instead of <TT>mod_privacy</TT>.
</UL>
You can find more
<A HREF="http://www.ejabberd.im/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>
<!--TOC subsection Common Options-->
<H3 CLASS="subsection"><A NAME="htoc37">3.3.2</A>&nbsp;&nbsp;Common Options</H3><!--SEC END -->
<A NAME="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"><TT>iqdisc</TT></H4><!--SEC END -->
<A NAME="modiqdiscoption"></A>
Many modules define handlers for processing IQ queries of different namespaces
to this server or to a user (e.&nbsp;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>{queues, N}</TT></B><DD CLASS="dd-description">: N separate queues are created to process the
queries. The queries are thus process in parallel, but in a
controlled way.
<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>host</TT>-->
<H4 CLASS="subsubsection"><TT>host</TT></H4><!--SEC END -->
<A NAME="modhostoption"></A>
This option defines the Jabber ID of a service provided by an <TT>ejabberd</TT> module.
The keyword "@HOST@" is replaced at start time with the real virtual host string.<BR>
<BR>
This example configures
the echo module to provide its echoing service
in the Jabber ID <TT>mirror.example.org</TT>:
<PRE CLASS="verbatim">
{modules,
[
...
{mod_echo, [{host, "mirror.example.org"}]},
...
]}.
</PRE>
However, if there are several virtual hosts and this module is enabled in all of them,
the "@HOST@" keyword must be used:
<PRE CLASS="verbatim">
{modules,
[
...
{mod_echo, [{host, "mirror.@HOST@"}]},
...
]}.
</PRE>
<!--TOC subsection <TT>mod_announce</TT>-->
<H3 CLASS="subsection"><A NAME="htoc38">3.3.3</A>&nbsp;&nbsp;<TT>mod_announce</TT></H3><!--SEC END -->
<A NAME="modannounce"></A>
This module enables configured users to broadcast announcements and to set
the message of the day (MOTD).
Configured users can perform these actions with a
Jabber client either using Ad-hoc commands
or sending messages to specific JIDs.<BR>
<BR>
The Ad-hoc commands are listed in the Server Discovery.
For this feature to work, <TT>mod_adhoc</TT> must be enabled.<BR>
<BR>
The specific JIDs where messages can be sent are listed bellow.
The first JID in each entry will apply only to the specified virtual host
<TT>example.org</TT>, while the JID between brackets will apply to all virtual
hosts in ejabberd.
<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&nbsp;<A HREF="#modoffline">3.3.12</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_adhoc, []},
{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_adhoc, []},
{mod_announce, [{access, announce}]},
...
]}.
</PRE></UL>
Note that <TT>mod_announce</TT> can be resource intensive on large
deployments as it can broadcast lot of messages. This module should be
disabled for instances of <TT>ejabberd</TT> with hundreds of thousands users.<BR>
<BR>
<!--TOC subsection <TT>mod_disco</TT>-->
<H3 CLASS="subsection"><A NAME="htoc39">3.3.4</A>&nbsp;&nbsp;<TT>mod_disco</TT></H3><!--SEC END -->
<A NAME="moddisco"></A>
This module adds support for Service Discovery (<A HREF="http://www.xmpp.org/extensions/xep-0030.html">XEP-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.xmpp.org/extensions/xep-0011.html">XEP-0011</A>) and Agent Information
(<A HREF="http://www.xmpp.org/extensions/xep-0094.html">XEP-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&nbsp;<A HREF="#modiqdiscoption">3.3.2</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="htoc40">3.3.5</A>&nbsp;&nbsp;<TT>mod_echo</TT></H3><!--SEC END -->
<A NAME="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>host</TT></B><DD CLASS="dd-description"> This option defines the Jabber ID of the
service. If the <TT>host</TT> option is not specified, the Jabber ID will be the
hostname of the virtual host with the prefix `<TT>echo.</TT>'. The keyword "@HOST@"
is replaced at start time with the real virtual host name.
</DL>
Example: Mirror, mirror, on the wall, who is the most beautiful
of them all?
<PRE CLASS="verbatim">
{modules,
[
...
{mod_echo, [{host, "mirror.example.org"}]},
...
]}.
</PRE>
<!--TOC subsection <TT>mod_http_bind</TT>-->
<H3 CLASS="subsection"><A NAME="htoc41">3.3.6</A>&nbsp;&nbsp;<TT>mod_http_bind</TT></H3><!--SEC END -->
<A NAME="modhttpbind"></A>
This module implements XMPP over Bosh (formerly known as HTTP Binding)
as outlined by <A HREF="http://www.xmpp.org/extensions/xep-0206.html">XEP-0206</A>.
It extends ejabberd's built in HTTP service with a configurable
resource at which this service will be hosted.<BR>
<BR>
To use HTTP-Binding, enable the module:
<PRE CLASS="verbatim">
{modules,
[
...
{mod_http_bind, []},
...
]}.
</PRE>and add <CODE>http_bind</CODE> in the HTTP service. For example:
<PRE CLASS="verbatim">
{listen,
[
...
{5280, ejabberd_http, [
http_bind,
http_poll,
web_admin
]
},
...
]}.
</PRE>With this configuration, the module will serve the requests sent to
<CODE>http://example.org:5280/http-bind/</CODE>
Remember that this page is not designed to be used by web browsers,
it is used by Jabber clients that support XMPP over Bosh.<BR>
<BR>
If you want to set the service in a different URI path or use a different module,
you can configure it manually using the option <CODE>request_handlers</CODE>.
For example:
<PRE CLASS="verbatim">
{listen,
[
...
{5280, ejabberd_http, [
{request_handlers, [{["http-bind"], mod_http_bind}]},
http_poll,
web_admin
]
},
...
]}.
</PRE>
<!--TOC subsection <TT>mod_http_fileserver</TT>-->
<H3 CLASS="subsection"><A NAME="htoc42">3.3.7</A>&nbsp;&nbsp;<TT>mod_http_fileserver</TT></H3><!--SEC END -->
<A NAME="modhttpfileserver"></A>
This simple module serves files from the local disk over HTTP.<BR>
<BR>
Options:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>docroot</TT></B><DD CLASS="dd-description">
Directory to serve the files.
<DT CLASS="dt-description"><B><TT>accesslog</TT></B><DD CLASS="dd-description">
File to log accesses using an Apache-like format.
No log will be recorded if this option is not specified.
</DL>
This example configuration will serve the files from
the local directory <CODE>/var/www</CODE>
in the address <CODE>http://example.org:5280/pub/archive/</CODE>.
To use this module you must enable it:
<PRE CLASS="verbatim">
{modules,
[
...
{mod_http_fileserver, [
{docroot, "/var/www"},
{accesslog, "/var/log/ejabberd/access.log"}
]
},
...
]}.
</PRE>And define it as a handler in the HTTP service:
<PRE CLASS="verbatim">
{listen,
[
...
{5280, ejabberd_http, [
...
{request_handlers, [
...
{["pub", "archive"], mod_http_fileserver},
...
]
},
...
]
},
...
]}.
</PRE>
<!--TOC subsection <TT>mod_irc</TT>-->
<H3 CLASS="subsection"><A NAME="htoc43">3.3.8</A>&nbsp;&nbsp;<TT>mod_irc</TT></H3><!--SEC END -->
<A NAME="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.xmpp.org/extensions/xep-0045.html">XEP-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>host</TT></B><DD CLASS="dd-description"> This option defines the Jabber ID of the
service. If the <TT>host</TT> option is not specified, the Jabber ID will be the
hostname of the virtual host with the prefix `<TT>irc.</TT>'. The keyword "@HOST@"
is replaced at start time with the real virtual host name.
<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>).
<DT CLASS="dt-description"><B><TT>default_encoding</TT></B><DD CLASS="dd-description"> Set the default IRC encoding (default value: <TT>"koi8-r"</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. The default encoding is set to "iso8859-15".
<PRE CLASS="verbatim">
{modules,
[
...
{mod_irc, [{access, all}, {default_encoding, "iso8859-15"}]},
...
]}.
</PRE><LI CLASS="li-itemize">In next example the IRC transport is available with JIDs with prefix <TT>irc-t.net</TT>.
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},
{host, "irc.example.net"}]},
...
]}.
</PRE></UL>
<!--TOC subsection <TT>mod_last</TT>-->
<H3 CLASS="subsection"><A NAME="htoc44">3.3.9</A>&nbsp;&nbsp;<TT>mod_last</TT></H3><!--SEC END -->
<A NAME="modlast"></A>
This module adds support for Last Activity (<A HREF="http://www.xmpp.org/extensions/xep-0012.html">XEP-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&nbsp;<A HREF="#modiqdiscoption">3.3.2</A>).
</DL>
<!--TOC subsection <TT>mod_muc</TT>-->
<H3 CLASS="subsection"><A NAME="htoc45">3.3.10</A>&nbsp;&nbsp;<TT>mod_muc</TT></H3><!--SEC END -->
<A NAME="modmuc"></A>
With this module enabled, your server will support Multi-User Chat
(<A HREF="http://www.xmpp.org/extensions/xep-0045.html">XEP-0045</A>). End users will be able to join text conferences.<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>
The MUC service allows any Jabber ID to register a nickname,
so nobody else can use that nickname in any room in the MUC service.
To register a nickname, open the Service Discovery in your
Jabber client and Register in the MUC service.<BR>
<BR>
The MUC service allows the service administrator to send a message
to all existing chatrooms.
To do so, send the message to the Jabber ID of the MUC service.<BR>
<BR>
This module supports clustering and load
balancing. One module can be started per cluster node. Rooms are
distributed at creation time on all available MUC module
instances. The multi-user chat module is clustered but the room
themselves are not clustered nor fault-tolerant: if the node managing a
set of rooms goes down, the rooms disappear and they will be recreated
on an available node on first connection attempt.<BR>
<BR>
Options:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>host</TT></B><DD CLASS="dd-description"> This option defines the Jabber ID of the
service. If the <TT>host</TT> option is not specified, the Jabber ID will be the
hostname of the virtual host with the prefix `<TT>conference.</TT>'. The keyword "@HOST@"
is replaced at start time with the real virtual host name.
<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_persistent</TT></B><DD CLASS="dd-description"> To configure who is
allowed to modify the 'persistent' chatroom option
(by default, everybody is allowed to modify that option).
<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.<BR>
<BR>
<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.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>max_users</TT></B><DD CLASS="dd-description"> This option defines at
the server level, the maximum number of users allowed per MUC
room. It can be lowered in each room configuration but cannot be
increased in individual MUC room configuration. The default value is
200.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>max_users_admin_threshold</TT></B><DD CLASS="dd-description">
This option defines the
number of MUC admins or owners to allow to enter the room even if
the maximum number of allowed users is reached. The default limits
is 5. In most cases this default value is the best setting.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>max_user_conferences</TT></B><DD CLASS="dd-description">
This option define the maximum
number of chat room any given user will be able to join. The default
is 10. This option is used to prevent possible abuses. Note that
this is a soft limits: Some users can sometime join more conferences
in cluster configurations.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>min_message_interval</TT></B><DD CLASS="dd-description">
This option defines the minimum interval between two messages send
by a user in seconds. This option is global and valid for all chat
rooms. A decimal value can be used. When this option is not defined,
message rate is not limited. This feature can be used to protect a
MUC service from users abuses and limit number of messages that will
be broadcasted by the service. A good value for this minimum message
interval is 0.4 second. If a user tries to send messages faster, an
error is send back explaining that the message have been discarded
and describing the reason why the message is not acceptable.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>min_presence_interval</TT></B><DD CLASS="dd-description">
This option defines the
minimum of time between presence changes coming from a given user in
seconds. This option is global and valid for all chat rooms. A
decimal value can be used. When this option is not defined, no
restriction is applied. This option can be used to protect a MUC
service for users abuses, as fastly changing a user presence will
result in possible large presence packet broadcast. If a user tries
to change its presence more often than the specified interval, the
presence is cached by <TT>ejabberd</TT> and only the last presence is
broadcasted to all users in the room after expiration of the
interval delay. Intermediate presence packets are silently
discarded. A good value for this option is 4 seconds.<BR>
<BR>
<DT CLASS="dt-description"><B><TT>default_room_options</TT></B><DD CLASS="dd-description"> This
option allow to define the desired default room options. Obviously,
the room creator can modify the room options at any time. The
available room options are: <TT>allow_change_subj</TT>,
<TT>allow_private_messages</TT>, <TT>allow_query_users</TT>,
<TT>allow_user_invites</TT>, <TT>anonymous</TT>, <TT>logging</TT>,
<TT>members_by_default</TT>, <TT>members_only</TT>,
<TT>moderated</TT>, <TT>password</TT>, <TT>password_protected</TT>,
<TT>persistent</TT>, <TT>public</TT>, <TT>public_list</TT>,
<TT>title</TT>. All of them can be set to <TT>true</TT> or
<TT>false</TT>, except <TT>password</TT> and <TT>title</TT> which
are strings.
</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><BR>
<BR>
<LI CLASS="li-itemize">In the following example, MUC anti abuse options are used. A
user cannot send more than one message every 0.4 seconds and cannot
change its presence more than once every 4 seconds. No ACLs are
defined, but some user restriction could be added as well:
<PRE CLASS="verbatim">
...
{modules,
[
...
{mod_muc, [{min_message_interval, 0.4},
{min_presence_interval, 4}]},
...
]}.
</PRE><BR>
<BR>
<LI CLASS="li-itemize">This example shows how to use <TT>default_room_options</TT> to make sure
newly created chatrooms have by default those options.
<PRE CLASS="verbatim">
{modules,
[
...
{mod_muc, [{access, muc_access},
{access_create, muc_admins},
{default_room_options, [
{allow_change_subj, false},
{allow_query_users, true},
{allow_private_messages, true},
{members_by_default, false},
{title, "New chatroom"},
{anonymous, false}
]},
{access_admin, muc_admins}]},
...
]}.
</PRE></UL>
<!--TOC subsection <TT>mod_muc_log</TT>-->
<H3 CLASS="subsection"><A NAME="htoc46">3.3.11</A>&nbsp;&nbsp;<TT>mod_muc_log</TT></H3><!--SEC END -->
<A NAME="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>spam_prevention</TT></B><DD CLASS="dd-description">
To prevent spam, the <TT>spam_prevention</TT> option adds a special attribute
to links that prevent their indexation by search engines. The default value
is <TT>true</TT>, which mean that nofollow attributes will be added to user
submitted links.
<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>&lt;a href="http://www.jabber.ru"&gt;Jabber.ru&lt;/a&gt;</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},
{spam_prevention, true},
{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>&lt;a href="/"&gt;Home&lt;/a&gt;</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="htoc47">3.3.12</A>&nbsp;&nbsp;<TT>mod_offline</TT></H3><!--SEC END -->
<A NAME="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&nbsp;<A HREF="#ejabberdctl">4.1</A>).
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>user_max_messages</TT></B><DD CLASS="dd-description">This option
is use to set a max number of offline messages per user (quota). Its
value can be either <TT>infinity</TT> or a strictly positive
integer. The default value is <TT>infinity</TT>.
</DL>
<!--TOC subsection <TT>mod_privacy</TT>-->
<H3 CLASS="subsection"><A NAME="htoc48">3.3.13</A>&nbsp;&nbsp;<TT>mod_privacy</TT></H3><!--SEC END -->
<A NAME="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&nbsp;<A HREF="#modiqdiscoption">3.3.2</A>).
</DL>
<!--TOC subsection <TT>mod_private</TT>-->
<H3 CLASS="subsection"><A NAME="htoc49">3.3.14</A>&nbsp;&nbsp;<TT>mod_private</TT></H3><!--SEC END -->
<A NAME="modprivate"></A>
This module adds support for Private XML Storage (<A HREF="http://www.xmpp.org/extensions/xep-0049.html">XEP-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.xmpp.org/extensions/xep-0048.html">XEP-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&nbsp;<A HREF="#modiqdiscoption">3.3.2</A>).
</DL>
<!--TOC subsection <TT>mod_proxy65</TT>-->
<H3 CLASS="subsection"><A NAME="htoc50">3.3.15</A>&nbsp;&nbsp;<TT>mod_proxy65</TT></H3><!--SEC END -->
<A NAME="modproxy"></A>
This module implements SOCKS5 Bytestreams (<A HREF="http://www.xmpp.org/extensions/xep-0065.html">XEP-0065</A>).
It allows <TT>ejabberd</TT> to act as a file transfer proxy between two
XMPP clients.<BR>
<BR>
Options:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>host</TT></B><DD CLASS="dd-description">This option defines the hostname of the service.
If this option is not set, the prefix `<TT>proxy.</TT>' is added to <TT>ejabberd</TT>
hostname.
<DT CLASS="dt-description"><B><TT>name</TT></B><DD CLASS="dd-description">Defines Service Discovery name of the service.
Default is <TT>"SOCKS5 Bytestreams"</TT>.
<DT CLASS="dt-description"><B><TT>ip</TT></B><DD CLASS="dd-description">This option specifies which network interface
to listen for. Default is an IP address of the service's DNS name, or,
if fails, <CODE>{127,0,0,1}</CODE>.
<DT CLASS="dt-description"><B><TT>port</TT></B><DD CLASS="dd-description">This option defines port to listen for
incoming connections. Default is&nbsp;7777.
<DT CLASS="dt-description"><B><TT>auth_type</TT></B><DD CLASS="dd-description">SOCKS5 authentication type.
Possible values are <TT>anonymous</TT> and <TT>plain</TT>. Default is
<TT>anonymous</TT>.
<DT CLASS="dt-description"><B><TT>access</TT></B><DD CLASS="dd-description">Defines ACL for file transfer initiators.
Default is <TT>all</TT>.
<DT CLASS="dt-description"><B><TT>max_connections</TT></B><DD CLASS="dd-description">Maximum number of
active connections per file transfer initiator. No limit by default.
<DT CLASS="dt-description"><B><TT>shaper</TT></B><DD CLASS="dd-description">This option defines shaper for
the file transfer peers. Shaper with the maximum bandwidth will be selected.
Default is <TT>none</TT>.
</DL>
Examples:
<UL CLASS="itemize"><LI CLASS="li-itemize">
The simpliest configuration of the module:
<PRE CLASS="verbatim">
{modules,
[
...
{mod_proxy65, []},
...
]}.
</PRE><LI CLASS="li-itemize">More complicated configuration.
<PRE CLASS="verbatim">
{acl, proxy_users, {server, "example.org"}}.
{access, proxy65_access, [{allow, proxy_users}, {deny, all}]}.
...
{acl, admin, {user, "admin", "example.org"}}.
{shaper, normal, {maxrate, 10240}}. %% 10 Kbytes/sec
{access, proxy65_shaper, [{none, admin}, {normal, all}]}.
...
{modules,
[
...
{mod_proxy65, [{host, "proxy1.example.org"},
{name, "File Transfer Proxy"},
{ip, {200,150,100,1}},
{port, 7778},
{max_connections, 5},
{access, proxy65_access},
{shaper, proxy65_shaper}]},
...
]}.
</PRE></UL>
<!--TOC subsection <TT>mod_pubsub</TT>-->
<H3 CLASS="subsection"><A NAME="htoc51">3.3.16</A>&nbsp;&nbsp;<TT>mod_pubsub</TT></H3><!--SEC END -->
<A NAME="modpubsub"></A>
This module offers a Publish-Subscribe Service (<A HREF="http://www.xmpp.org/extensions/xep-0060.html">XEP-0060</A>).
The functionality in <TT>mod_pubsub</TT> can be extended using plugins.
The plugin that implements PEP (Personal Eventing via Pubsub) (<A HREF="http://www.xmpp.org/extensions/xep-0163.html">XEP-0163</A>)
is enabled by default, and requires <TT>mod_caps</TT>.<BR>
<BR>
Options:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>host</TT></B><DD CLASS="dd-description"> This option defines the Jabber ID of the
service. If the <TT>host</TT> option is not specified, the Jabber ID will be the
hostname of the virtual host with the prefix `<TT>pubsub.</TT>'. The keyword "@HOST@"
is replaced at start time with the real virtual host name.
<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>. <DT CLASS="dt-description"><B><TT>plugins</TT></B><DD CLASS="dd-description"> To specify which pubsub node plugins to use. If not defined, the default
pubsub plugin is always used.
<DT CLASS="dt-description"><B><TT>nodetree</TT></B><DD CLASS="dd-description"> To specify which nodetree to use. If not defined, the default pubsub
nodetree is used. Nodetrees are default and virtual. Only one nodetree can be used
and is shared by all node plugins.
</DL>
Example:
<PRE CLASS="verbatim">
{modules,
[
...
{mod_pubsub, [
{access_createnode, pubsub_createnode},
{plugins, ["default", "pep"]}
]}
...
]}.
</PRE>
<!--TOC subsection <TT>mod_register</TT>-->
<H3 CLASS="subsection"><A NAME="htoc52">3.3.17</A>&nbsp;&nbsp;<TT>mod_register</TT></H3><!--SEC END -->
<A NAME="modregister"></A>
This module adds support for In-Band Registration (<A HREF="http://www.xmpp.org/extensions/xep-0077.html">XEP-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 denied. (there are no
restrictions by default).
<DT CLASS="dt-description"><B><TT>welcome_message</TT></B><DD CLASS="dd-description"> Set a welcome message that
is sent to each newly registered account. The first string is the subject, and
the second string is the message body.
<DT CLASS="dt-description"><B><TT>registration_watchers</TT></B><DD CLASS="dd-description"> This option defines a
list of JIDs which will be notified each time a new account is registered.
<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&nbsp;<A HREF="#modiqdiscoption">3.3.2</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><LI CLASS="li-itemize">Define the welcome message and three registration watchers:
<PRE CLASS="verbatim">
{modules,
[
...
{mod_register, [
{welcome_message, {"Welcome!", "Welcome to this Jabber server. For information about Jabber visit http://www.jabber.org"}},
{registration_watchers, ["admin1@example.org", "admin2@example.org", "boss@example.net"]}
]},
...
]}.
</PRE></UL>
<!--TOC subsection <TT>mod_roster</TT>-->
<H3 CLASS="subsection"><A NAME="htoc53">3.3.18</A>&nbsp;&nbsp;<TT>mod_roster</TT></H3><!--SEC END -->
<A NAME="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&nbsp;<A HREF="#modiqdiscoption">3.3.2</A>).
</DL>
<!--TOC subsection <TT>mod_service_log</TT>-->
<H3 CLASS="subsection"><A NAME="htoc54">3.3.19</A>&nbsp;&nbsp;<TT>mod_service_log</TT></H3><!--SEC END -->
<A NAME="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>&lt;route/&gt;</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="htoc55">3.3.20</A>&nbsp;&nbsp;<TT>mod_shared_roster</TT></H3><!--SEC END -->
<A NAME="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.
A shared roster group can have members from any Jabber server,
but the presence will only be available from and to members
of the same virtual host where the group is created.<BR>
<BR>
Shared roster groups can be edited <EM>only</EM> via the Web Admin. 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 Admin.
To put as members all the registered users in the virtual hosts,
you can use the special directive: @all@.
Note that this directive is designed for a small server with just a few hundred users.
<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. Additionally, 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>&nbsp;</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="htoc56">3.3.21</A>&nbsp;&nbsp;<TT>mod_stats</TT></H3><!--SEC END -->
<A NAME="modstats"></A>
This module adds support for Statistics Gathering (<A HREF="http://www.xmpp.org/extensions/xep-0039.html">XEP-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&nbsp;<A HREF="#modiqdiscoption">3.3.2</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 XEP, 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">
&lt;iq to='example.org' type='get'&gt;
&lt;query xmlns='http://jabber.org/protocol/stats'&gt;
&lt;stat name='users/online'/&gt;
&lt;/query&gt;
&lt;/iq&gt;
</PRE><LI CLASS="li-itemize">You can request the total number of registered users on all virtual hosts
by sending:
<PRE CLASS="verbatim">
&lt;iq to='example.org' type='get'&gt;
&lt;query xmlns='http://jabber.org/protocol/stats'&gt;
&lt;stat name='users/all-hosts/total'/&gt;
&lt;/query&gt;
&lt;/iq&gt;
</PRE></UL>
<!--TOC subsection <TT>mod_time</TT>-->
<H3 CLASS="subsection"><A NAME="htoc57">3.3.22</A>&nbsp;&nbsp;<TT>mod_time</TT></H3><!--SEC END -->
<A NAME="modtime"></A>
This module features support for Entity Time (<A HREF="http://www.xmpp.org/extensions/xep-0090.html">XEP-0090</A>). By using this XEP,
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&nbsp;<A HREF="#modiqdiscoption">3.3.2</A>).
</DL>
<!--TOC subsection <TT>mod_vcard</TT>-->
<H3 CLASS="subsection"><A NAME="htoc58">3.3.23</A>&nbsp;&nbsp;<TT>mod_vcard</TT></H3><!--SEC END -->
<A NAME="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.xmpp.org/extensions/xep-0054.html">XEP-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>host</TT></B><DD CLASS="dd-description"> This option defines the Jabber ID of the
service. If the <TT>host</TT> option is not specified, the Jabber ID will be the
hostname of the virtual host with the prefix `<TT>vjud.</TT>'. The keyword "@HOST@"
is replaced at start time with the real virtual host name.
<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&nbsp;<A HREF="#modiqdiscoption">3.3.2</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>host</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>.
This option is available in <TT>mod_vcard</TT>, but not available in <TT>mod_vcard_odbc</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="htoc59">3.3.24</A>&nbsp;&nbsp;<TT>mod_vcard_ldap</TT></H3><!--SEC END -->
<A NAME="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&nbsp;<A HREF="#ldapauth">3.2.5</A>).<BR>
<BR>
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_uids</TT>, and
<TT>ldap_filter</TT>. See section&nbsp;<A HREF="#ldapauth">3.2.5</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.<BR>
<BR>
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>host</TT></B><DD CLASS="dd-description"> This option defines the Jabber ID of the
service. If the <TT>host</TT> option is not specified, the Jabber ID will be the
hostname of the virtual host with the prefix `<TT>vjud.</TT>'. The keyword "@HOST@"
is replaced at start time with the real virtual host name.
<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&nbsp;<A HREF="#modiqdiscoption">3.3.2</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>host</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>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"]},
{"LAST", "%s", ["sn"]},
{"FIRST", "%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", "FIRST"},
{"Middle Name", "MIDDLE"},
{"Family Name", "LAST"},
{"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> &mdash; email address, <TT>"givenName"</TT>
&mdash; first name, <TT>"sn"</TT> &mdash; second name, <TT>"birthDay"</TT> &mdash; 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"},
%% uidattr: user's part of JID is located in the "mail" attribute
%% uidattr_format: common format for our emails
{ldap_uids, [{"mail","%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
{"FIRST", "%s", ["givenName"]},
{"LAST", "%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="htoc60">3.3.25</A>&nbsp;&nbsp;<TT>mod_version</TT></H3><!--SEC END -->
<A NAME="modversion"></A>
This module implements Software Version (<A HREF="http://www.xmpp.org/extensions/xep-0092.html">XEP-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>show_os</TT></B><DD CLASS="dd-description">Should the operating system be revealed or not.
The default value is <TT>true</TT>.
<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&nbsp;<A HREF="#modiqdiscoption">3.3.2</A>).
</DL>
<!--TOC chapter Managing an <TT>ejabberd</TT> server-->
<H1 CLASS="chapter"><A NAME="htoc61">Chapter&nbsp;4</A>&nbsp;&nbsp;Managing an <TT>ejabberd</TT> server</H1><!--SEC END -->
<!--TOC section <TT>ejabberdctl</TT>-->
<H2 CLASS="section"><A NAME="htoc62">4.1</A>&nbsp;&nbsp;<TT>ejabberdctl</TT></H2><!--SEC END -->
<A NAME="ejabberdctl"></A>
<!--TOC subsection Commands-->
<H3 CLASS="subsection"><A NAME="htoc63">4.1.1</A>&nbsp;&nbsp;Commands</H3><!--SEC END -->
<A NAME="commands"></A>
The <TT>ejabberdctl</TT> command line script allows to start, stop and perform
many other administrative tasks in a local or remote <TT>ejabberd</TT> server.<BR>
<BR>
When <TT>ejabberdctl</TT> is executed without any parameter,
it displays the available options. If there isn't an <TT>ejabberd</TT> server running,
the available parameters are:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>start</TT></B><DD CLASS="dd-description"> Start <TT>ejabberd</TT> in background mode. This is the default method.
<DT CLASS="dt-description"><B><TT>debug</TT></B><DD CLASS="dd-description"> Attach an Erlang shell to an already existing <TT>ejabberd</TT> server. This allows to execute commands interactively in the <TT>ejabberd</TT> server.
<DT CLASS="dt-description"><B><TT>live</TT></B><DD CLASS="dd-description"> Start <TT>ejabberd</TT> in live mode: the shell keeps attached to the started server, showing log messages and allowing to execute interactive commands.
</DL>
If there is an <TT>ejabberd</TT> server running in the system,
<TT>ejabberdctl</TT> shows all the available commands in that server.
The more interesting ones are:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>status</TT></B><DD CLASS="dd-description"> Check the status of the <TT>ejabberd</TT> server.
<DT CLASS="dt-description"><B><TT>stop</TT></B><DD CLASS="dd-description"> Stop the <TT>ejabberd</TT> server which is running in the machine.
<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://www.ejabberd.im/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>
The <TT>ejabberdctl</TT> script also allows the argument <TT>&ndash;node NODENAME</TT>.
This allows to administer a remote node.<BR>
<BR>
The <TT>ejabberdctl</TT> administration script can be configured in the file ejabberdctl.cfg.
This file provides detailed information about each configurable option.<BR>
<BR>
<!--TOC subsection Erlang runtime system-->
<H3 CLASS="subsection"><A NAME="htoc64">4.1.2</A>&nbsp;&nbsp;Erlang runtime system</H3><!--SEC END -->
<A NAME="erlangconfiguration"></A>
<TT>ejabberd</TT> is an Erlang/OTP application that runs inside an Erlang runtime system.
This system is configured using environment variables and command line parameters.
The <TT>ejabberdctl</TT> administration script uses many of those possibilities.
You can configure some of them with the file <TT>ejabberdctl.cfg</TT>,
which includes detailed description about them.
This section describes for reference purposes
all the environment variables and command line parameters.<BR>
<BR>
The environment variables:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>EJABBERD_CONFIG_PATH</TT></B><DD CLASS="dd-description">
Path to the ejabberd configuration file.
<DT CLASS="dt-description"><B><TT>EJABBERD_MSGS_PATH</TT></B><DD CLASS="dd-description">
Path to the directory with translated strings.
<DT CLASS="dt-description"><B><TT>EJABBERD_LOG_PATH</TT></B><DD CLASS="dd-description">
Path to the ejabberd service log file.
<DT CLASS="dt-description"><B><TT>EJABBERD_SO_PATH</TT></B><DD CLASS="dd-description">
Path to the directory with binary system libraries.
<DT CLASS="dt-description"><B><TT>HOME</TT></B><DD CLASS="dd-description">
Path to the directory that is considered <TT>ejabberd</TT>'s home.
This path is used to read the file <TT>.erlang.cookie</TT>.
<DT CLASS="dt-description"><B><TT>ERL_CRASH_DUMP</TT></B><DD CLASS="dd-description">
Path to the file where crash reports will be dumped.
<DT CLASS="dt-description"><B><TT>ERL_INETRC</TT></B><DD CLASS="dd-description">
Indicates which IP name resolution to use.
If using <TT>-sname</TT>, specify either this option or <TT>-kernel inetrc filepath</TT>.
<DT CLASS="dt-description"><B><TT>ERL_MAX_PORTS</TT></B><DD CLASS="dd-description">
Maximum number of simultaneously open Erlang ports.
<DT CLASS="dt-description"><B><TT>ERL_MAX_ETS_TABLES</TT></B><DD CLASS="dd-description">
Maximum number of ETS and Mnesia tables.
</DL>
The command line parameters:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>-sname ejabberd</TT></B><DD CLASS="dd-description">
The Erlang node will be identified using only the first part
of the host name, i.&nbsp;e. other Erlang nodes outside this domain cannot contact
this node. This is the preferable option in most cases.
<DT CLASS="dt-description"><B><TT>-name ejabberd</TT></B><DD CLASS="dd-description">
The Erlang node will be fully identified.
This is only useful if you plan to setup an <TT>ejabberd</TT> cluster with nodes in different networks.
<DT CLASS="dt-description"><B><TT>-kernel inetrc "/etc/ejabberd/inetrc"</TT></B><DD CLASS="dd-description">
Indicates which IP name resolution to use.
If using <TT>-sname</TT>, specify either this option or <TT>ERL_INETRC</TT>.
<DT CLASS="dt-description"><B><TT>-kernel inet_dist_listen_min 4200 inet_dist_listen_min 4210</TT></B><DD CLASS="dd-description">
Define the first and last ports that <TT>epmd</TT> (section <A HREF="#epmd">5.2</A>) can listen to.
<DT CLASS="dt-description"><B><TT>-detached</TT></B><DD CLASS="dd-description">
Starts the Erlang system detached from the system console.
Useful for running daemons and backgrounds processes.
<DT CLASS="dt-description"><B><TT>-noinput</TT></B><DD CLASS="dd-description">
Ensures that the Erlang system never tries to read any input.
Useful for running daemons and backgrounds processes.
<DT CLASS="dt-description"><B><TT>-pa /var/lib/ejabberd/ebin</TT></B><DD CLASS="dd-description">
Specify the directory where Erlang binary files (*.beam) are located.
<DT CLASS="dt-description"><B><TT>-s ejabberd</TT></B><DD CLASS="dd-description">
Tell Erlang runtime system to start the <TT>ejabberd</TT> application.
<DT CLASS="dt-description"><B><TT>-mnesia dir "/var/lib/ejabberd/db/nodename"</TT></B><DD CLASS="dd-description">
Specify the Mnesia database directory.
<DT CLASS="dt-description"><B><TT>-sasl sasl_error_logger {file, "/var/log/ejabberd/sasl.log"}</TT></B><DD CLASS="dd-description">
Path to the Erlang/OTP system log file.
<DT CLASS="dt-description"><B><TT>+K [true|false]</TT></B><DD CLASS="dd-description">
Kernel polling.
<DT CLASS="dt-description"><B><TT>-smp [auto|enable|disable]</TT></B><DD CLASS="dd-description">
SMP support.
<DT CLASS="dt-description"><B><TT>+P 250000</TT></B><DD CLASS="dd-description">
Maximum number of Erlang processes.
<DT CLASS="dt-description"><B><TT>-remsh ejabberd@localhost</TT></B><DD CLASS="dd-description">
Open an Erlang shell in a remote Erlang node.
</DL>
Note that some characters need to be escaped when used in shell scripts, for instance <CODE>"</CODE> and <CODE>{}</CODE>.
You can find other options in the Erlang manual page (<TT>erl -man erl</TT>).<BR>
<BR>
<!--TOC section Web Admin-->
<H2 CLASS="section"><A NAME="htoc65">4.2</A>&nbsp;&nbsp;Web Admin</H2><!--SEC END -->
<A NAME="webadmin"></A>
The <TT>ejabberd</TT> Web Admin allows to administer most of <TT>ejabberd</TT> using a web browser.<BR>
<BR>
This feature is enabled by default:
a <TT>ejabberd_http</TT> listener with the option <TT>web_admin</TT> (see
section&nbsp;<A HREF="#listened">3.1.3</A>) is included in the listening ports. 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&nbsp;<A HREF="#fig:webadmmain">4.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 4.1: Top page from the Web Admin</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 Admin 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 Admin
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 Admin on a secured
connection, on a port differing from the HTTP Polling interface, and bind it
to the internal LAN IP. The Web Admin 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 section Ad-hoc Commands-->
<H2 CLASS="section"><A NAME="htoc66">4.3</A>&nbsp;&nbsp;Ad-hoc Commands</H2><!--SEC END -->
<A NAME="adhoccommands"></A>
If you enable <TT>mod_configure</TT> and <TT>mod_adhoc</TT>,
you can perform several administrative tasks in <TT>ejabberd</TT>
with a Jabber client.
The client must support Ad-Hoc Commands (<A HREF="http://www.xmpp.org/extensions/xep-0050.html">XEP-0050</A>),
and you must login in the Jabber server with
an account with proper privileges.<BR>
<BR>
<!--TOC section Change Computer Hostname-->
<H2 CLASS="section"><A NAME="htoc67">4.4</A>&nbsp;&nbsp;Change Computer Hostname</H2><!--SEC END -->
<A NAME="changeerlangnodename"></A>
<TT>ejabberd</TT> uses the distributed Mnesia database.
Being distributed, Mnesia enforces consistency of its file,
so it stores the name of the Erlang node in it.
The name of an Erlang node includes the hostname of the computer.
So, the name of the Erlang node changes
if you change the name of the machine in which <TT>ejabberd</TT> runs,
or when you move <TT>ejabberd</TT> to a different machine.<BR>
<BR>
So, if you want to change the computer hostname where <TT>ejabberd</TT> is installed,
you must follow these instructions:
<OL CLASS="enumerate" type=1><LI CLASS="li-enumerate">
In the old server, backup the Mnesia database using the Web Admin or <TT>ejabberdctl</TT>.
For example:
<PRE CLASS="verbatim">
ejabberdctl backup /tmp/ejabberd-oldhost.backup
</PRE> <LI CLASS="li-enumerate">In the new server, restore the backup file using the Web Admin or <TT>ejabberdctl</TT>.
For example:
<PRE CLASS="verbatim">
ejabberdctl restore /tmp/ejabberd-oldhost.backup
</PRE></OL>
<!--TOC chapter Securing <TT>ejabberd</TT>-->
<H1 CLASS="chapter"><A NAME="htoc68">Chapter&nbsp;5</A>&nbsp;&nbsp;Securing <TT>ejabberd</TT></H1><!--SEC END -->
<!--TOC section Firewall Settings-->
<H2 CLASS="section"><A NAME="htoc69">5.1</A>&nbsp;&nbsp;Firewall Settings</H2><!--SEC END -->
<A NAME="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>Standard port for Jabber/XMPP client connections, plain or STARTTLS.</TD>
</TR>
<TR><TD ALIGN=left NOWRAP>5223</TD>
<TD ALIGN=left NOWRAP>Standard port for Jabber client connections using the old SSL method.</TD>
</TR>
<TR><TD ALIGN=left NOWRAP>5269</TD>
<TD ALIGN=left NOWRAP>Standard port for Jabber/XMPP server connections.</TD>
</TR>
<TR><TD ALIGN=left NOWRAP>4369</TD>
<TD ALIGN=left NOWRAP>EPMD (section <A HREF="#epmd">5.2</A>) listens for Erlang node name requests.</TD>
</TR>
<TR><TD ALIGN=left NOWRAP>port range</TD>
<TD ALIGN=left NOWRAP>Used for connections between Erlang nodes. This range is configurable (see section <A HREF="#epmd">5.2</A>).</TD>
</TR></TABLE>
<DIV CLASS="center"><HR WIDTH="80%" SIZE=2></DIV></DIV></BLOCKQUOTE>
<!--TOC section epmd -->
<H2 CLASS="section"><A NAME="htoc70">5.2</A>&nbsp;&nbsp;epmd </H2><!--SEC END -->
<A NAME="epmd"></A>
<A HREF="http://www.erlang.org/doc/man/epmd.html">epmd (Erlang Port Mapper Daemon)</A>
is a small name server included in Erlang/OTP
and used by Erlang programs when establishing distributed Erlang communications.
<TT>ejabberd</TT> needs <TT>epmd</TT> to use <TT>ejabberdctl</TT> and also when clustering <TT>ejabberd</TT> nodes.
This small program is automatically started by Erlang, and is never stopped.
If <TT>ejabberd</TT> is stopped, and there aren't any other Erlang programs
running in the system, you can safely stop <TT>epmd</TT> if you want.<BR>
<BR>
<TT>ejabberd</TT> runs inside an Erlang node.
To communicate with <TT>ejabberd</TT>, the script <TT>ejabberdctl</TT> starts a new Erlang node
and connects to the Erlang node that holds <TT>ejabberd</TT>.
In order for this communication to work,
<TT>epmd</TT> must be running and listening for name requests in the port 4369.
You should block the port 4369 in the firewall in such a way that
only the programs in your machine can access it.<BR>
<BR>
If you build a cluster of several <TT>ejabberd</TT> instances,
each <TT>ejabberd</TT> instance is called an <TT>ejabberd</TT> node.
Those <TT>ejabberd</TT> nodes use a special Erlang communication method to
build the cluster, and EPMD is again needed listening in the port 4369.
So, if you plan to build a cluster of <TT>ejabberd</TT> nodes
you must open the port 4369 for the machines involved in the cluster.
Remember to block the port so Internet doesn't have access to it.<BR>
<BR>
Once an Erlang node solved the node name of another Erlang node using EPMD and port 4369,
the nodes communicate directly.
The ports used in this case by default are random,
but can be configured in the file <TT>ejabberdctl.cfg</TT>.
The Erlang command-line parameter used internally is, for example:
<PRE CLASS="verbatim">
erl ... -kernel inet_dist_listen_min 4370 inet_dist_listen_max 4375
</PRE>
<!--TOC section Erlang Cookie-->
<H2 CLASS="section"><A NAME="htoc71">5.3</A>&nbsp;&nbsp;Erlang Cookie</H2><!--SEC END -->
<A NAME="cookie"></A>
The Erlang cookie is a string with numbers and letters.
An Erlang node reads the cookie at startup from the command-line parameter <TT>-setcookie</TT>
or from a cookie file.
Two Erlang nodes communicate only if they have the same cookie.
Setting a cookie on the Erlang node allows you to structure your Erlang network
and define which nodes are allowed to connect to which.<BR>
<BR>
Thanks to Erlang cookies, you can prevent access to the Erlang node by mistake,
for example when there are several Erlang nodes running different programs in the same machine.<BR>
<BR>
Setting a secret cookie is a simple method
to difficult unauthorized access to your Erlang node.
However, the cookie system is not ultimately effective
to prevent unauthorized access or intrusion to an Erlang node.
The communication between Erlang nodes are not encrypted,
so the cookie could be read sniffing the traffic on the network.
The recommended way to secure the Erlang node is to block the port 4369.<BR>
<BR>
<!--TOC section Erlang node name-->
<H2 CLASS="section"><A NAME="htoc72">5.4</A>&nbsp;&nbsp;Erlang node name</H2><!--SEC END -->
<A NAME="nodename"></A>
An Erlang node may have a node name.
The name can be short (if indicated with the command-line parameter <TT>-sname</TT>)
or long (if indicated with the parameter <TT>-name</TT>).
Starting an Erlang node with -sname limits the communication between Erlang nodes to the LAN.<BR>
<BR>
Using the option <TT>-sname</TT> instead of <TT>-name</TT> is a simple method
to difficult unauthorized access to your Erlang node.
However, it is not ultimately effective to prevent access to the Erlang node,
because it may be possible to fake the fact that you are on another network
using a modified version of Erlang <TT>epmd</TT>.
The recommended way to secure the Erlang node is to block the port 4369.<BR>
<BR>
<!--TOC chapter Clustering-->
<H1 CLASS="chapter"><A NAME="htoc73">Chapter&nbsp;6</A>&nbsp;&nbsp;Clustering</H1><!--SEC END -->
<A NAME="clustering"></A>
<!--TOC section How it Works-->
<H2 CLASS="section"><A NAME="htoc74">6.1</A>&nbsp;&nbsp;How it Works</H2><!--SEC END -->
<A NAME="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 subsection Router-->
<H3 CLASS="subsection"><A NAME="htoc75">6.1.1</A>&nbsp;&nbsp;Router</H3><!--SEC END -->
<A NAME="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 subsection Local Router-->
<H3 CLASS="subsection"><A NAME="htoc76">6.1.2</A>&nbsp;&nbsp;Local Router</H3><!--SEC END -->
<A NAME="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 subsection Session Manager-->
<H3 CLASS="subsection"><A NAME="htoc77">6.1.3</A>&nbsp;&nbsp;Session Manager</H3><!--SEC END -->
<A NAME="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 subsection s2s Manager-->
<H3 CLASS="subsection"><A NAME="htoc78">6.1.4</A>&nbsp;&nbsp;s2s Manager</H3><!--SEC END -->
<A NAME="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 section Clustering Setup-->
<H2 CLASS="section"><A NAME="htoc79">6.2</A>&nbsp;&nbsp;Clustering Setup</H2><!--SEC END -->
<A NAME="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 Admin.<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 &mdash; 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 Service Load-Balancing-->
<H2 CLASS="section"><A NAME="htoc80">6.3</A>&nbsp;&nbsp;Service Load-Balancing</H2><!--SEC END -->
<!--TOC subsection Components Load-Balancing-->
<H3 CLASS="subsection"><A NAME="htoc81">6.3.1</A>&nbsp;&nbsp;Components Load-Balancing</H3><!--SEC END -->
<A NAME="componentlb"></A>
<!--TOC subsection Domain Load-Balancing Algorithm-->
<H3 CLASS="subsection"><A NAME="htoc82">6.3.2</A>&nbsp;&nbsp;Domain Load-Balancing Algorithm</H3><!--SEC END -->
<A NAME="domainlb"></A>
<TT>ejabberd</TT> includes an algorithm to load balance the components that are plugged on an <TT>ejabberd</TT> cluster. It means that you can plug one or several instances of the same component on each <TT>ejabberd</TT> cluster and that the traffic will be automatically distributed.<BR>
<BR>
The default distribution algorithm try to deliver to a local instance of a component. If several local instances are available, one instance is chosen randomly. If no instance is available locally, one instance is chosen randomly among the remote component instances.<BR>
<BR>
If you need a different behaviour, you can change the load balancing behaviour with the option <TT>domain_balancing</TT>. The syntax of the option is the following:
<PRE CLASS="verbatim">
{domain_balancing, "component.example.com", &lt;balancing_criterium&gt;}.
</PRE>
Several balancing criteria are available:
<UL CLASS="itemize"><LI CLASS="li-itemize">
<TT>destination</TT>: the full JID of the packet <TT>to</TT> attribute is used.
<LI CLASS="li-itemize"><TT>source</TT>: the full JID of the packet <TT>from</TT> attribute is used.
<LI CLASS="li-itemize"><TT>bare_destination</TT>: the bare JID (without resource) of the packet <TT>to</TT> attribute is used.
<LI CLASS="li-itemize"><TT>bare_source</TT>: the bare JID (without resource) of the packet <TT>from</TT> attribute is used.
</UL>
If the value corresponding to the criteria is the same, the same component instance in the cluster will be used.<BR>
<BR>
<!--TOC subsection Load-Balancing Buckets-->
<H3 CLASS="subsection"><A NAME="htoc83">6.3.3</A>&nbsp;&nbsp;Load-Balancing Buckets</H3><!--SEC END -->
<A NAME="lbbuckets"></A>
When there is a risk of failure for a given component, domain balancing can cause service trouble. If one component is failing the service will not work correctly unless the sessions are rebalanced.<BR>
<BR>
In this case, it is best to limit the problem to the sessions handled by the failing component. This is what the <TT>domain_balancing_component_number</TT> option does, making the load balancing algorithm not dynamic, but sticky on a fix number of component instances.<BR>
<BR>
The syntax is the following:
<PRE CLASS="verbatim">
{domain_balancing_component_number, "component.example.com", N}
</PRE>
<!--TOC chapter Debugging-->
<H1 CLASS="chapter"><A NAME="htoc84">Chapter&nbsp;7</A>&nbsp;&nbsp;Debugging</H1><!--SEC END -->
<A NAME="debugging"></A>
<!--TOC section Watchdog Alerts-->
<H2 CLASS="section"><A NAME="htoc85">7.1</A>&nbsp;&nbsp;Watchdog Alerts</H2><!--SEC END -->
<A NAME="watchdog"></A>
<TT>ejabberd</TT> includes a watchdog mechanism.
If a process in the <TT>ejabberd</TT> server consumes too much memory,
a message is sent to the Jabber accounts defined with the option
<TT>watchdog_admins</TT>
in the <TT>ejabberd</TT> configuration file.
Example configuration:
<PRE CLASS="verbatim">
{watchdog_admins, ["admin2@localhost", "admin2@example.org"]}.
</PRE>
<!--TOC section Log Files-->
<H2 CLASS="section"><A NAME="htoc86">7.2</A>&nbsp;&nbsp;Log Files</H2><!--SEC END -->
<A NAME="logfiles"></A>
An <TT>ejabberd</TT> node writes two log files:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>ejabberd.log</TT></B><DD CLASS="dd-description"> is the ejabberd service log, with the messages reported by <TT>ejabberd</TT> code
<DT CLASS="dt-description"><B><TT>sasl.log</TT></B><DD CLASS="dd-description"> is the Erlang/OTP system log, with the messages reported by Erlang/OTP using SASL (System Architecture Support Libraries)
</DL>
The option <TT>loglevel</TT> modifies the verbosity of the file ejabberd.log.
The possible levels are:
<DL CLASS="description" COMPACT=compact><DT CLASS="dt-description">
<B><TT>0</TT></B><DD CLASS="dd-description"> No ejabberd log at all (not recommended)
<DT CLASS="dt-description"><B><TT>1</TT></B><DD CLASS="dd-description"> Critical
<DT CLASS="dt-description"><B><TT>2</TT></B><DD CLASS="dd-description"> Error
<DT CLASS="dt-description"><B><TT>3</TT></B><DD CLASS="dd-description"> Warning
<DT CLASS="dt-description"><B><TT>4</TT></B><DD CLASS="dd-description"> Info
<DT CLASS="dt-description"><B><TT>5</TT></B><DD CLASS="dd-description"> Debug
</DL>
For example, the default configuration is:
<PRE CLASS="verbatim">
{loglevel, 4}.
</PRE>
<!--TOC section Debug Console-->
<H2 CLASS="section"><A NAME="htoc87">7.3</A>&nbsp;&nbsp;Debug Console</H2><!--SEC END -->
<A NAME="debugconsole"></A>
The Debug Console is an Erlang shell attached to an already running <TT>ejabberd</TT> server.
With this Erlang shell, an experienced administrator can perform complex tasks.<BR>
<BR>
This shell gives complete control over the <TT>ejabberd</TT> server,
so it is important to use it with extremely care.
There are some simple and safe examples in the article
<A HREF="http://www.ejabberd.im/interconnect-erl-nodes">Interconnecting Erlang Nodes</A><BR>
<BR>
To exit the shell, close the window or press the keys: control+c control+c.<BR>
<BR>
<!--TOC chapter Internationalization and Localization-->
<H1 CLASS="chapter"><A NAME="htoc88">Appendix&nbsp;A</A>&nbsp;&nbsp;Internationalization and Localization</H1><!--SEC END -->
<A NAME="i18nl10n"></A>
All built-in modules support the <TT>xml:lang</TT> attribute inside IQ queries.
Figure&nbsp;<A HREF="#fig:discorus">A.1</A>, for example, shows the reply to the following query:
<PRE CLASS="verbatim">
&lt;iq id='5'
to='example.org'
type='get'
xml:lang='ru'&gt;
&lt;query xmlns='http://jabber.org/protocol/disco#items'/&gt;
&lt;/iq&gt;
</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 A.1: 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 Admin also supports the <CODE>Accept-Language</CODE> HTTP header.
<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 A.2: Web Admin showing a virtual host when the web browser provides the
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 chapter Release Notes-->
<H1 CLASS="chapter"><A NAME="htoc89">Appendix&nbsp;B</A>&nbsp;&nbsp;Release Notes</H1><!--SEC END -->
<A NAME="releasenotes"></A>
Release notes are available from <A HREF="http://www.process-one.net/en/ejabberd/release_notes/">ejabberd Home Page</A><BR>
<BR>
<!--TOC chapter Acknowledgements-->
<H1 CLASS="chapter"><A NAME="htoc90">Appendix&nbsp;C</A>&nbsp;&nbsp;Acknowledgements</H1><!--SEC END -->
<A NAME="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@process-one.net"><TT>xmpp:mremond@process-one.net</TT></A>)
<LI CLASS="li-itemize">Sander Devrieze (<A HREF="xmpp:s.devrieze@gmail.com"><TT>xmpp:s.devrieze@gmail.com</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 chapter Copyright Information-->
<H1 CLASS="chapter"><A NAME="htoc91">Appendix&nbsp;D</A>&nbsp;&nbsp;Copyright Information</H1><!--SEC END -->
<A NAME="copyright"></A>
Ejabberd Installation and Operation Guide.<BR>
Copyright <20> 2003 &mdash; 2008 Process-one<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>
View Git Blame Copy Permalink