Changes between Version 2 and Version 3 of LdapPluginTests
- Timestamp:
- Nov 5, 2005, 11:18:55 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LdapPluginTests
v2 v3 5 5 == Prerequistes == 6 6 7 The examples in this page assume sthat 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:7 The examples in this page assume 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 with a separate package) namely: 9 9 * server tools: `slapadd`, `slapcat` 10 10 * client tools: `ldapsearch`, `ldapadd`, `ldapmodify`, `ldapdelete` … … 14 14 == Create the directory config file == 15 15 16 The following config file is somewhat more complex tha t it could be, as it usedACL, 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 ;-)16 The following config file is somewhat more complex than it could be, as it uses 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 ;-) 18 18 19 19 {{{ … … 90 90 == Configure your system logger == 91 91 92 OpenLDAP errors are somewhat cryptic. You can find useful information fromthe log produced by the server.92 OpenLDAP errors are somewhat cryptic. You can find useful information in the log produced by the server. 93 93 94 94 It 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 ;-)95 If an ldapsearch request fails, blame your server configuration (or your directory content) not the Trac Ldap Extension ;-) 96 96 97 97 1. Add the following entry in `/etc/syslog.conf` … … 122 122 You 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. 123 123 124 If everything is ok, shut down the server right now, 'cose we need to initialize the LDAP directory124 If everything is ok, shut down the server right now, because we need to initialize the LDAP directory 125 125 126 126 == Initializing the directory == … … 137 137 objectClass: organization 138 138 }}} 139 1. Then , inject this LDIF data into the LDAP directory,using the server tool. '''Yes''', the server should be down at this very moment139 1. Then inject this LDIF data into the LDAP directory using the server tool. '''Yes''', the server should be down at this very moment 140 140 {{{ 141 141 /usr/sbin/slapadd -b "dc=example,dc=org" -l init.ldif … … 201 201 objectClass: tracuser 202 202 }}} 203 1. Add those entries to the directory ,using the client tool. This won't work if the LDAP server is down203 1. Add those entries to the directory using the client tool. This won't work if the LDAP server is down 204 204 {{{ 205 205 ldapadd -D "uid=root,dc=example,dc=org" -x -W -f direst.ldif … … 210 210 1. Search entries using an anonymous bind: 211 211 {{{ 212 212 213 ldapsearch -b "dc=example,dc=org" -x objectclass=* 213 214 }}} … … 218 219 }}} 219 220 220 1. You can also add new entries , and removesthem if you like. But do not forget that the Ldap Extension unit tests expect the directory to be set up as described up to now221 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 221 222 222 223 == Clean up == 223 224 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.225 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. 225 226 226 227 1. Shut down the OpenLDAP server … … 236 237 237 238 [[TagIt(eblot,0.9)]] 238