From: Art Cancro Date: Sat, 27 Mar 2004 02:21:32 +0000 (+0000) Subject: *** empty log message *** X-Git-Tag: v7.86~5498 X-Git-Url: https://code.citadel.org/?a=commitdiff_plain;h=c31a166cf5678a1edae2cf1691fac32ea90e5f50;p=citadel.git *** empty log message *** --- diff --git a/citadel/docs/citadel.html b/citadel/docs/citadel.html index 063100d58..a3c33af6f 100644 --- a/citadel/docs/citadel.html +++ b/citadel/docs/citadel.html @@ -1934,7 +1934,12 @@ Citadel system.

In order to prevent "just anyone" from subscribing to any room on your system, there is a setting in the .Aide Edit room command:

-
CitaNews} . Aide Edit this room
Room name [CitaNews]:

(lots of other stuff omitted for brevity...)

Self-service list subscribe/unsubscribe [No]: Yes
+
CitaNews} . Aide Edit this room

+Room name [CitaNews]:

+

+(lots of other stuff omitted for brevity...)

+

+Self-service list subscribe/unsubscribe [No]: Yes

When you answer "Yes" to self-service list subscribe/unsubscribe, you are enabling that feature. Now, all you have to do is tell the world about @@ -2357,9 +2362,64 @@ and running before you attempt to connect Citadel to it.

Configuring the LDAP Connector for Citadel

-FIXME   finish writing this
+Once you've located or installed your LDAP server, connecting Citadel +to it is easily completed with the .Aide System-configuration +General command:
+ +
Lobby> . Aide System configuration General

(lots of other stuff omitted for brevity...)

Connect this Citadel to an LDAP directory [Yes]: Yes
Host name of LDAP server []: 127.0.0.1
Port number of LDAP service [389]: 389
Base DN []: dc=servername,dc=domain,dc=org
Bind DN []: cn=manager,dc=servername,dc=domain,dc=org
Password for bind DN []: secret

(more questions omitted...)

Save this configuration? Yes
+Once you've done this, restart your Citadel service with the .Aide Terminate-server +Now command.  When +Citadel restarts, it will connect to your LDAP directory.  Note +that we gave Citadel the same Base DN, Bind DN, and password that was +in our LDAP server configuration example.  Obviously, everything +needs to be identical on both sides or the connection will be +refused.  127.0.0.1 is the loopback address, and 389 is the +standard port number for LDAP, so this would be the proper host and +port combination for an LDAP service running on your local +server.  It could just as easily be on another server, for example +an organization-wide directory server.
+
+You can also configure the LDAP Connector for Citadel from a WebCit +session.  Log on as an Aide and click on Advanced Options --> +Edit Site-Wide Configuration --> Directory, and you will be +presented with the same set of questions.
+
+So, what kind of information will be entered into LDAP?  As a +rule, anything that gets saved to your Global Address Book room will +also be saved to LDAP.  Citadel will set up OU's (Organizational +Units) for each node on your Citadel network, so if you are running +multiple Citadel servers in an organization, you will automatically +have a hierarchial view built for you.  Below the OU's will be an +entry for each user who has a vCard registered on the system.  +Citadel automatically translates vCard information to LDAP.

+If you already have a Global Address Book full of existing information, +you can execute an IGAB +(Initialize Global Address Book) server command to rebuild it.  In +addition to performing its usual function of rebuilding the internal +Internet e-mail address mapping table, Citadel will also repopulate +LDAP with all existing vCards.  You should be aware, however, that +existing LDAP entries will not be cleared from your directory +server.  If your directory contains only Citadel data, you can +safely delete your database and start over, because it will be +repopulated.  Otherwise, Citadel will merely update any existing +records with fresh information.

+The LDAP Connector for Citadel is a recent development, so expect more +functionality in this space in the near future.