Changes between Version 2 and Version 3 of LdapPluginTests


Ignore:
Timestamp:
Nov 5, 2005, 11:18:55 PM (18 years ago)
Author:
Emmanuel Blot
Comment:

Typo/grammar

Legend:

Unmodified
Added
Removed
Modified
  • LdapPluginTests

    v2 v3  
    55== Prerequistes ==
    66
    7 The examples in this page assumes that you are working with a Linux server (Debian), with OpenLDAP 2.2 or greater.[[BR]]
    8 The `slapd` server should have been installed, and you should also have access to the Ldap utils (which usually comes within a separate package), namely:
     7The examples in this page assume that you are working with a Linux server (Debian), with OpenLDAP 2.2 or greater.[[BR]]
     8The `slapd` server should have been installed and you should also have access to the Ldap utils (which usually comes with a separate package) namely:
    99 * server tools: `slapadd`, `slapcat`
    1010 * client tools: `ldapsearch`, `ldapadd`, `ldapmodify`, `ldapdelete`
     
    1414== Create the directory config file ==
    1515
    16 The following config file is somewhat more complex that it could be, as it used ACL, etc.[[BR]]
    17 However, this is a good base to elaborate a more complex LDAP setup, and ... that's the file I use to test the extension ;-)
     16The following config file is somewhat more complex than it could be, as it uses ACL, etc.[[BR]]
     17However this is a good base to elaborate a more complex LDAP setup and ... that's the file I use to test the extension ;-)
    1818
    1919{{{
     
    9090== Configure your system logger ==
    9191
    92 OpenLDAP errors are somewhat cryptic. You can find useful information from the log produced by the server.
     92OpenLDAP errors are somewhat cryptic. You can find useful information in the log produced by the server.
    9393
    9494It is very useful to compare requests made by standard utilities such as `ldapsearch` and the requests made by the extension:[[BR]]
    95 If a ldapsearch request fails, blame your server configuration (or your directory content), not the Trac Ldap Extension ;-)
     95If an ldapsearch request fails, blame your server configuration (or your directory content) not the Trac Ldap Extension ;-)
    9696
    9797 1. Add the following entry in `/etc/syslog.conf`
     
    122122You should not get any error. If you get an error message (carefully check the log file), please fix up your LDAP configuration before resuming installation.
    123123
    124 If everything is ok, shut down the server right now, 'cose we need to initialize the LDAP directory
     124If everything is ok, shut down the server right now, because we need to initialize the LDAP directory
    125125
    126126== Initializing the directory ==
     
    137137objectClass: organization
    138138}}}
    139  1. Then, inject this LDIF data into the LDAP directory, using the server tool. '''Yes''', the server should be down at this very moment
     139 1. Then inject this LDIF data into the LDAP directory using the server tool. '''Yes''', the server should be down at this very moment
    140140{{{
    141141/usr/sbin/slapadd -b "dc=example,dc=org" -l init.ldif
     
    201201objectClass: tracuser
    202202}}}
    203  1. Add those entries to the directory, using the client tool. This won't work if the LDAP server is down
     203 1. Add those entries to the directory using the client tool. This won't work if the LDAP server is down
    204204{{{
    205205ldapadd -D "uid=root,dc=example,dc=org" -x -W -f direst.ldif
     
    210210 1. Search entries using an anonymous bind:
    211211{{{
     212
    212213ldapsearch -b "dc=example,dc=org" -x objectclass=*
    213214}}}
     
    218219}}}
    219220
    220  1. You can also add new entries, and removes them if you like. But do not forget that the Ldap Extension unit tests expect the directory to be set up as described up to now
     221 1. You can also add new entries and remove them if you like. But do not forget that the Ldap Extension unit tests expect the directory to be set up as described up to now
    221222
    222223== Clean up ==
    223224
    224 If the test fails, or some part of the installation procedure fails, you want to clean up the LDAP directory, to restart from a clean environment.
     225If the test fails or some part of the installation procedure fails, you want to clean up the LDAP directory to restart from a clean environment.
    225226
    226227 1. Shut down the OpenLDAP server
     
    236237
    237238[[TagIt(eblot,0.9)]]
    238