summaryrefslogtreecommitdiff
path: root/Architecture_and_Design/en-US/Kolab_Daemon.xml
blob: 2650ab313d1a838a82592c47f3994e6b713795e1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Architecture_and_Design.ent">
%BOOK_ENTITIES;
]>
<chapter id="chap-Architecture_and_Design-Kolab_Daemon">
    <title>Kolab Daemon</title>
    <para>
        The Kolab daemon is a multi-process daemon that synchronizes the authentication and authorization database mutations with various aspects of a Kolab Groupware deployment.
    </para>
    <para>
        Using the <literal>[ldap]</literal> <literal>domain_*</literal> settings, (domain_base_dn, domain_search_filter, domain_search_scope, domain_name_attribute, ...), the Kolab daemon determines the number of authentication databases for which to render service, as each domain name space may require either a switch in authn/authz technology, or different bind credentials.
    </para>
    <note>
        This functionality is currently limited to LDAP only.
    </note>
    <para>
        To illustrate, one of its responsibilities is to make sure adding a new user is propagated in the form of a new mailbox.
    </para>
    <para>
        The master process determines the number of domain name spaces served from different authentication and authorization sources.
    </para>
    <para>
        For LDAP based deployments, this includes multiple domain name spaces served with different root dns.
    </para>
    <para>
        It uses /etc/kolab/kolab.conf, section ldap, keys domain_base_dn, domain_rootdn_attribute, domain_filter, domain_name_attribute.
    </para>
</chapter>