This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Installation and Upgrades / eBox installation in combination with existing LDAP Server
« on: April 16, 2009, 06:50:17 pm »
Hello,
I am trying to set up an eBox-Mailserver in combination with an existing LDAP-Server. The ebox version is 1.0 on top of a ubuntu 8.04 LTS.
I have several servers running in my network for different tasks:
The servers pdc, egw and egw-db are already running. Now I have just started with the mail-server and try to setup the userandgroups-module with the existing ldap-server. I have already tried to change the values in the sourcecode and yes, I know that these changes will be overwritten by an update:
File ldap.pm:
use constant DN => "dc=domain";
use constant LDAP => "ldap://ip-adress of mail";
File UsersandGroups.pm:
use constant USERSDN => 'ou=users';
use constant GROUPSDN => 'ou=groups';
I have changed the password in /var/lib/ebox/conf/ebox-ldap.passwd to the correct one.
When I try to edit a user the result is:
An internal error has ocurred. This is most probably a bug, relevant information can be found in the logs.
An internal error related to a template has occurred. This is a bug, relevant information can be found in the logs.
When I try to edit groups the result is:
An internal error has ocurred. This is most probably a bug, relevant information can be found in the logs.
Further information:
What else do I have to change to get this running?
It is not very charming, to set up several ldap-servers and to create the same useraccount on several servers. If there is no way to get this working as I tried to, I will have to setup an ldap-server on the mail server and a slurpd environment on each other server. But this is not the way I like it, because the pdc should do the authentication.
For further assistence I will be thankful.
best regards
Daniel
I am trying to set up an eBox-Mailserver in combination with an existing LDAP-Server. The ebox version is 1.0 on top of a ubuntu 8.04 LTS.
I have several servers running in my network for different tasks:
server | description | ebox |
pdc | openLDAP-server for authentication | no |
egw | Groupware-server with the egroupware installation 1.6.0 with existing ldap connection | yes |
egw-db | database-server for egroupware | no |
mail-server for egroupware with postfix, courier, fetchmail | yes |
The servers pdc, egw and egw-db are already running. Now I have just started with the mail-server and try to setup the userandgroups-module with the existing ldap-server. I have already tried to change the values in the sourcecode and yes, I know that these changes will be overwritten by an update:
File ldap.pm:
use constant DN => "dc=domain";
use constant LDAP => "ldap://ip-adress of mail";
File UsersandGroups.pm:
use constant USERSDN => 'ou=users';
use constant GROUPSDN => 'ou=groups';
I have changed the password in /var/lib/ebox/conf/ebox-ldap.passwd to the correct one.
When I try to edit a user the result is:
An internal error has ocurred. This is most probably a bug, relevant information can be found in the logs.
An internal error related to a template has occurred. This is a bug, relevant information can be found in the logs.
When I try to edit groups the result is:
An internal error has ocurred. This is most probably a bug, relevant information can be found in the logs.
Further information:
- There is no firewall or something else running, which can block the connection. With phpldapadmin I can connect to the ldap-server on the pdc and to the ldap running on the mail server.
- The slapd.conf files are identical except the schema includes for egroupware.
What else do I have to change to get this running?
It is not very charming, to set up several ldap-servers and to create the same useraccount on several servers. If there is no way to get this working as I tried to, I will have to setup an ldap-server on the mail server and a slurpd environment on each other server. But this is not the way I like it, because the pdc should do the authentication.
For further assistence I will be thankful.
best regards
Daniel
Pages: [1]