Subject: The mailing list for listmasters using Sympa
List archive
- From: Anthony Hess <address@concealed>
- To: <address@concealed>
- Subject: Re: [sympa-users] Ldap auth and archives broken
- Date: Tue, 29 Mar 2005 11:48:12 -0700
Title: Re: [sympa-users] Ldap auth and archives broken To respond to my own thread (from late January) for the googlers out there:
I finally got back to this and I think Ive made some progress. Ive resolved the original problem I think, but there is another related issue. I will submit another mail for that one to keep things clean.
Here is more info that I sent offlist:
********
Here is what I had when I tailed the log.
Feb 15 10:19:12 fugazi wwsympa[530]: [client 150.135.173.134] do_home
Feb 15 10:19:23 fugazi wwsympa[543]: [client 150.135.173.134] do_login(tonyh)
Feb 15 10:19:23 fugazi wwsympa[543]: Skipping empty auth.conf
Feb 15 10:19:23 fugazi wwsympa[543]: [client 150.135.173.134] Incorrect Ldap password
Feb 15 10:19:23 fugazi wwsympa[543]: Authentication failed
Feb 15 10:19:23 fugazi wwsympa[543]: [client 150.135.173.134] do_loginrequest
The auth.conf is certainly not empty (and I didn’t see any leading spaces or weird characters in the file itself). Googling on that error only gave me the line in the wwsympa auth.pm that contains that code to generate that error.
Here are the permissions on the file:
-rw-r----- 1 sympa sympa 440 Jan 29 07:16 auth.conf
*****
I just installed the latest sympa version and made sure the permissions looked like that and now it works. So Im not sure if one of the developers fixed a bug or what happened. Anyway, so now ldap auth and archives work again. Only one problem – now people can’t log in from the user table! Im going to just create another issue for that one since its something different.
Tony
- Re: [sympa-users] Ldap auth and archives broken, Anthony Hess, 03/29/2005
Archive powered by MHonArc 2.6.19+.