• Welcome to SAIL Community Supported PBX . Please login or sign up.
 
March 29, 2024, 05:30:43 AM

News:

SMF updated to 2.0


S200 Upgrade to latest, Ldap install

Started by drifting, March 09, 2016, 05:13:49 PM

Previous topic - Next topic

drifting

March 09, 2016, 05:13:49 PM Last Edit: March 09, 2016, 05:16:32 PM by drifting
Hi.
I have followed the Wiki to the letter on install for 4.1 which, I was informed was not Beta now? not only on an s200 but also a virtual deb install (Test machine) I get Ldap failure.

Set domain to myserver.local in network tab.

Installed sail as instructed, version now 4.1.0-10, also armel,39

Further down the document is states to install Ldap, but this was installed by the Sail package already.

Did set the domain name to myserver.local and checking on the  /opt/sark/cache/ldapcontactou.ldif
dn: ou=contacts,dc=myserver,dc=local
objectClass: organizationalUnit
objectClass: top
ou: contacts

Ran this from a troubleshooting article for LDAP
ldapsearch -Y EXTERNAL -H ldapi:/// -b cn=config

And the above within that is right. dc's etc.

Any idea where to troubleshoot this problem? as there is no other message displayed other than Ldap error, other than when I try to enter something :- saildeb/admin - LDAP ERROR - Strong(er) authentication required

Must admit I am not too bothered about the debian test machine, so if you have a later image for the s200 with it installed, that would be good.

Regards P

drifting

Well, not sure this was right thing to do.

Stopped LDAP
remove /var/lib/ldap files except DB_CONFIG
Ran dpkg-reconfigure slapd
Set the name and domain properly
Continued with the instructions from this site.

root@saildeb:/var/lib/ldap# slapadd -l /opt/sark/cache/ldapcontactou.ldif
56f12875 ldif_read_file: checksum error on "/etc/ldap/slapd.d/cn=config.ldif"
_#################### 100.00% eta   none elapsed            none fast!         
Closing DB...Error, entries missing!
  entry 1: dc=saildeb,dc=testicles,dc=local

Seems the error can be ignored? But hopefully sysadmin here will confirm?

Rebooted and all is now well. Even now I have no idea what I did wrong in the first instant, the warning was pretty apt in the article, as I had no idea how to fault find. Google is your friend in these moments.

P




sysadmin

If you are working with a SARK200 then as long as it is 4.1 or better, LDAP will be already installed when you take it out of the box.  For a self install then you must follow the instructions on the wiki.  For LDAP to work you must add an OU with a dc of "contacts" (as detailed in the wiki).   You must also set the LDAP base in Globals.   You can verify the base by running slapcat from the Linux console.   The first line of output gives the base.  In the example below the base is 'dc=aelintra,dc=local'.  Whatever is in your base is what you should put into Globals.

slapcat
dn: dc=aelintra,dc=local
objectClass: top
objectClass: dcObject
objectClass: organization
o: aelintra.local
dc: aelintra

 

drifting

Thanks for that further info Jeff.

Understand what was going on much better now.

Thanks

Paul.