Hi Alex, Disclaimer: the steps I included 'work for me' :)
On Thu, 2010-05-20 at 00:12 +0000, Alex Clark wrote: > On 2010-05-19, Tim Knapp <[email protected]> wrote: > > Hi Diego, > > > > You need to do the following: > > > > 1. Firstly we've got to install the pre-requisite packages required to > > get Plone talking to LDAP. > > So we need to install OpenLDAP on the Windows server as follows: > > i. Download the following Windows installer: > > http://download.bergmans.us/openldap/openldap-2.2.29/openldap-2.2.29-db-4.3.29- > > openssl-0.9.8a-win32_Setup.exe > > ii. Run the installer and install it to an appropriate location. It can > > be installed as a service > > but there's no need to have the service start automatically. Also, don't > > install slurpd. > > That is if you are running openldap on windows right? AFAIK, you don't > need to do this if you just want your Plone to connect to an openldap > elsewhere > > (this is in Chapter 4 of my book: > https://www.packtpub.com/plone-3-3-site-administration/book, > coming in June, I hope ;-)) Yeah, I don't think you necessarily need to install openldap on the target machine unless you're compiling your own python-ldap egg and the instructions I include below point to a pre-compiled egg but I did this 'just in case'. > > > 2. The following lines need to be inserted into the buildout.cfg. The > > '...' indicates that there will > > most probably be existing content already in there. Please also observe > > the indentation as > > despite looking pretty it also ensures the buildout will work. > > findlinks = > > ... > > http://svn.kmrc.de/download/distribution/contrib/ > > ? Who's repo is this? Dunno but if you go to www.kmrc.de it points to some kind of research/educational institute - again it 'just works' ;) > > > eggs = > > ... > > Products.LDAPUserFolder > > Products.LDAPMultiPlugins > > Products.PloneLDAP > > plone.app.ldap > > You only *really* need to list plone.app.ldap, it depends on the rest. Yeah, again this is a 'just in case' as iirc I read 'somewhere' on plone.org that the others need adding. > > > > [versions] > > ... > > python-ldap = 2.3.9 > > plone.app.ldap = 1.1 > > [instance] > > ... > > zcml = > > ... > > plone.app.ldap > > > > And then re-run buildout. > > I found that I had to install > http://pypi.python.org/packages/2.4/p/python-ldap/python-ldap-2.3.11.win32-py2.4.exe > because if I let my buildout install it, I got a DLL error. Using the steps above it shouldn't produce a DLL error as its a pre-compiled egg. > > But then I ended up in a situation where I could get Zope 2 to start, but > only by manually > removing the python-ldap eggs from eggs/ (and relying on the > package-installed python-ldap). > > I'm looking for a consistent way to reproduce this, thought. > > Because everytime I run Buildout I get the python-ldap egg back ;-) Again, my steps above should work. Only downer is that you have to pin the python-ldap version to an older version. If you want to save yourself a lot of headaches, though, use the Enfold Server 5.0 installer - that way its a walk in the park :) -Tim > > Alex > > > > > Thanks, > > Tim > > > > On Wed, 2010-05-19 at 08:20 -0700, didakus wrote: > >> I am trying to install Plone 3.2.2 with LDAP on a windows 2003 server. The > >> installation from the installer is fine. When I then edit the buildout.cfg > >> to include: plone.app.ldap and run buildout I get this error message: > >> file Lib\ldap\schema.py (for module ldap.schema) not found > >> error: Setup script exited with error: Python was built with Visual Studio > >> 2003; > >> extensions must be built with a compiler than can generate compatible > >> binaries. > >> Visual Studio 2003 was not found on this system. If you have Cygwin > >> installed, > >> you can try compiling with MingW32, by passing "-c mingw32" to setup.py. > >> > >> I have also tried adding products.ploneLDAP to the buildout in stead of > >> plone.app.ldap this results in another error from python. Python.exe unable > >> to locate component. This application has failed to start because > >> liblber.dll was not found. > >> > >> I have been searching everywhere for a solution but haven't found one so > >> far. Can anyone tell me what my buildout.cfg should look like to get LDAP > >> installed without the error messages mentioned above. > >> > >> If you need more information regarding my setup, let me know. > >> > >> Kind regards, D > >> > >> > > > > > > _______________________________________________ > > Setup mailing list > > [email protected] > > http://lists.plone.org/mailman/listinfo/setup > > _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
