acl_users folder (LDAP)

[Richard H.]

I've deleted the 'staff' Silva instance off arana (which was migrated from kumo and was only a test instance anyway) and I have created a new instances called uob_staff_test. This will be used to test the new functionality that will arise from the DL enhacements project - or at least, that's the plan!

I've been going through my notes on how to create a new Silva instance and get it to work with the DL and with LDAP and I have come across a problem. I will quickly outline what I've done so far:

Silva and DL

(i) Added a new Silva root called uob_staff_test
(ii) Added a new OAI PMH Service in uob_staff_test (linked to the staff DL on arana and using the 'harvest' account that we have created in LDAP specifically for harvesting)
(iii) Edited the new Service and added my email address for any harvesting or OAI PMH errors, and created a dl storage (but ignored oai_dc), then selected 'Change settings' and then 'Update'
(iv) Selected 'go to dl storage' and saw that docs where now in the list (i.e. Silva has successfully harvested from the relevant DL)

... in other words, that part seems to be working fine. However...

Silva and LDAP

(v) Gone to uob_staff_test 'Services' tab and deleted 'service_members' and then added 'Silva Bedfordshire LDAP MemberService'
(vi) Selected 'silva_extensions' from within 'Services' tab and selected install for 'SilvaBedfordshireLDAP'

At this point I'm sure there's meant to be an 'acl_users' folder within uob_staff_test, but all I'm seeing is a 'Members' folder? Without this folder I can't configure the LDAP server details into Silva.

Help?

(This was originally reported on August 21st '07 on the dl list)

[Richard H. (richard-hewison)]

Silva and DL (addendum)

I also installed three Silva extensions:

Silva External Sources
Silva OAI
Document Library Integration

[Richard H. (richard-hewison)]

This bug is currently a show stopper to the arana migration project. We must be able to get Silva and LDAP working together on arana ASAP. Can someone looks at this bug today?

[Eric Casteleijn (thisfred)]

Daniel, can you look at this today?

[Daniel Nouri (daniel.nouri)]

The 'acl_users' directory you're missing can be added through the ZMI. To do this, go into the Silva root and add an "LDAPUserFolder" by choosing it in the dropdown on the top right and clicking "Add".

Can you please post your notes on the installation somewhere. I'm thinking that this may mean two things:
  - Some part of the installation that's supposed to set up the LDAPUserFolder for you isn't doing it, or
  - this step is missing in your installation notes.

[Richard H. (richard-hewison)]

Daniel,

The point is that when you install the SilvaBedfordshireLDAP service extension, it is supposed to create a special version of the acl_users folder that, when selected, allows you to configure the LDAP server. At the moment, this isn't happening. Of course we can create an ordinary acl_users folder form the ZMI but that isn't the problem we're trying to solve!

>>> On 12/09/2007 at 16:42, Daniel Nouri <email address hidden> wrote:
> The 'acl_users' directory you're missing can be added through the ZMI.
> To do this, go into the Silva root and add an "LDAPUserFolder" by
> choosing it in the dropdown on the top right and clicking "Add".
>
> Can you please post your notes on the installation somewhere. I'm thinking
> that this may mean two things:
> - Some part of the installation that's supposed to set up the
> LDAPUserFolder for you isn't doing it, or
> - this step is missing in your installation notes.
>
> --
> acl_users folder (LDAP)
> https://bugs.launchpad.net/bugs/138558
> You received this bug notification because you are a direct subscriber
> of the bug.

[Richard H. (richard-hewison)]

My installation notes are already posted. My bug report (138558) contains a list of exactly what had been done up to the point where the acl_users folder wasn't available in Zope.

>>> On 12/09/2007 at 16:42, Daniel Nouri <email address hidden> wrote:

> Can you please post your notes on the installation somewhere. I'm thinking
> that this may mean two things:
> - Some part of the installation that's supposed to set up the
> LDAPUserFolder for you isn't doing it, or
> - this step is missing in your installation notes.
>
> --
> acl_users folder (LDAP)
> https://bugs.launchpad.net/bugs/138558
> You received this bug notification because you are a direct subscriber
> of the bug.

[Daniel Nouri (daniel.nouri)]

Richard, are you positive that SilvaBedfordshireLDAP is supposed to create an LDAPUserFolder/acl_users on installation? Looking into the code, I don't think it ever did this.

I would suggest you try and add an LDAPUserFolder (which *is* a special acl_users folder for LDAP authentication) through the ZMI and see if that solves your problem.

[Richard H. (richard-hewison)]

This whole thing is puzzling because I created a test Silva instance from scratch and I didn't manually add an LDAPUserFolder, yet one was there whilst I was trying to document the process after I added that particular extension.

In fact, I have a screenshot from this (attached) which is a subtly different screen to that which is used if I manually create one (as you suggest) and then go in and edit it afterwards (notice the Zope mapping option, and the fact that the User ID Attribute option is missing from the form you get when you create one manually on arana now).

Has anything changed on arana that would make this behave differently? Maybe a different Zope LDAP product or another upgrade that has changed this behaviour in some way? Creating the acl_users folder manually is *not* the same process that I followed when I created my 'test' Silva instance previously.

[Richard H. (richard-hewison)]

Okay, we now have a Silva instance on the test Zope instance working up to a point. However, there are some weird issues with it which we are going to list as a new 'bug', rather than append this one here. These issues might be because we have manually created the acl_usr folder and then again it might not be.

[Richard H. (richard-hewison)]

Although we now create the acl_usr folder ourselves, was anyone ever able to offer an explanation for why the process was subtly different before and why the user folder's appearance (and options) were different (if you look at the previously attached PNG file?)