Well I thought I had it all working but now I don't
I did have an Ubuntu and a Kubuntu virtual machine authenticating nicely from 
ebox but then I upgraded ebox to 1.3.10 which broke usersandgroups!
As I wanted to get 3 eboxes linked as master slave I decided to just start 
from the beginning and install ubuntu server 8.04 followed by the ebox modules 
I wanted.
I edited /etc/ebox/80samba.config to give a login shell of /bin/bash before 
creating any users. (or rather before setting up the relationship with the 
master ldap and letting them sync)

First of my WinXP machine could not authenticate but after some fiddling (can't 
now remember what I did) it then worked and continues to do so.

My linux machines, that did authenticate, now don't after changing the 
passwords in ldap.conf to match the new server.

On the PDC/ldap server I checked /etc/default/slapd
this line
SLAPD_SERVICES="ldap://0.0.0.0 ldapi://%2fvar%2frun%2fslapd%2fldapi/????x-
mod=0777"
I assumed meant my server was listening on all interfaces and all ports - I 
could search the server with no problems from any machine with ldap-utils 
installed.
The commented out line that one I edited to 
SLAPD_SERVICES="ldap://0.0.0.0:389/ ldaps:/// ldapi:///"
and commented out the line that was active
sudo /etc/init.d/slapd restart would not work as SLAPD_NO_START was set so I 
commented out this line and tried again but got this
administra...@eboxoffice:~$ sudo /etc/init.d/slapd restart
Stopping OpenLDAP: slapd.
Starting OpenLDAP: slapd - failed.
The operation failed but no output was produced. For hints on what went
wrong please refer to the system's logfiles (e.g. /var/log/syslog) or
try running the daemon in Debug mode like via "slapd -d 16383" (warning:
this will create copious output).

Below, you can find the command line options used by this script to
run slapd. Do not forget to specify those options if you
want to look to debugging output:
  slapd -h 'ldap://0.0.0.0:389/ ldaps:/// ldapi:///' -g openldap -u openldap -
F /etc/ldap/slapd.d/

However restarting the whole server with slapd_no_start set brought the ldap 
server up fine.
Still nothing from my previously working linux logins though.
After much fiddling, to no effect, I started with a fresh Karmic install and 
retraced the steps that gave me a working client last week - still did not 
work
I then tried installing ebox-desktop on an Ubuntu fresh install of karmic 
(friday ebox-desktop as not in the repository)
This also fails to authenticate

I am getting authentication failure unknown user so the clients seem to be 
talking to the ldap server but not finding the users in the database.

ebox-desktop set up ldap.conf to use a search base of cn=ebox (or dn=ebox I 
forget) so I tried changing this to ou=Users,dc=dcmc as this worked on my 
setup last week
I also tried setting ldap login required with the user cn=ebox,dc=dcmc as this 
also seemed necessary last week (PW from ldap.secret)

If I could manage to get ebox-desktop to work that would be fine or if I could 
manage to get a manual setup to work that would also be fine.
Having worked out the steps to do a manual setup last week I can't for the 
life of me figure out why it won't work this week

Any further ideas most welcome

Peter

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
ebox-user mailing list
[email protected]
http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user

Reply via email to