Re: Problem with Jamm-Cleaner.sh
"Keith T. Garner" <[email protected]> Thu, 15 Jul 2004 09:52:03 -0500
| Newsgroups | gmane.mail.jamm.user |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jul 15, 2004 at 03:47:04, Tristan DEFERT said: > mail:~ root# /etc/periodic/hourly/100.jammcleaner [snip] > Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - > Invalid Credentials] > > It seems that this cleanup script cannot connect to LDAP (localhost) Its connecting fine, its just not authenticating. :) > My question is: > - Does this script uses the Jamm Administrator login/pwd to connect to > LDAP server? Jamm cleaner works at the dn level, if only because in some setups, it would not (and should not) have access to the jamm.properties file from the webapp. The current version takes everything from the command line. Before 1.0 we should probably tweak it to take the settings from a file. jammCleaner needs at least the following options: -D,--dn the dn to bind with -b,--base base dn to search from -w,--password password to connect to LDAP with > - Can the Jamm Administrator login be different from "root" (e.g. > "admin" ) ? This is a different question that's not really related to jammCleaner. However, the answer is yes. That is configurable in the jamm.properties file. Its really just a shortcut for convince so you don't have to type the full DN out all the time. Keith -- Keith T. Garner [email protected] "Make no little plans; they have no magic to stir men's blood." - Daniel H. Burnham ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click