The issues queue suggests excellent developer responsiveness.

Several 6.x issue statuses are indicated as "fixed" or successfully tested by the community. Is a new 6.x release imminent?

I ask because my employer may be looking at using this module in a special Drupal install, but I want to defer if a new release is around the corner.

Comments

roball’s picture

Category: support » feature

I also think a new official 6.x release is now ready to succeed 1.0-alpha2. The current dev code is definitely more stable than alpha2.

aren cambre’s picture

Thanks! Does "new official 6.x release" mean you're skipping beta, going straight to production-ready release?

roball’s picture

Aren, as you can see at http://drupal.org/project/developers/15109, I don't belong to this module's developers. As that list shows, the only person currently maintaining it is miglius - all the others have not been active for one year or longer.

It seems that miglius' time on this module is also very limited, so all we can do is to hope seeing progress by him or someone joins to work with him.

johnbarclay’s picture

Title: Next release » Can we get Make LDAP Group to Role mapping configurable via web interface (node/318174) in this release...

Make LDAP Group to Role mapping configurable via web interface
http://drupal.org/node/318174

This wasn't on the list for the next release. Is there any way of getting it in? Would it help if I maintained the groups module separately?

For the testing process, we might want to use the ldap help module export our testing configurations. http://drupal.org/node/353036

miglius’s picture

Title: Can we get Make LDAP Group to Role mapping configurable via web interface (node/318174) in this release... » Next release

The issues I listed here are relatively small isolated ones, however the issue you're referring to, #318174: Make LDAP Group to Role mapping configurable via web interface is rather a rewrite of the groups module instead. I'm not convinced that OOP should be used for this case.

miglius’s picture

If anybody could help in testing the patches attached to the issues above, that would speed up the new release.

roball’s picture

Excellent! But what about releasing an beta1 first that includes all the efforts you have already done after alpha2?

miglius’s picture

Since I lot of changes going into this release, I'm planning about next alpha.

johnbarclay’s picture

I uninstalled and tested this version on Microsoft Active Directory LDAP on Drupal 6.10.

- The authentication part worked well.

- the "test" button doesn't retain your ldap configuration data. It clears it out and gives you an error. It should either say "save and test" and do both or say "test (but save your data first); whichever you're looking for.

- The ldap groups fails when mapping based on "Groups are specified by LDAP attributes" or "Groups exist as LDAP entries where a multivalued attribute contains the members' CNs". It also introduces case sensitivity which I believe is a bad thing. I believe the fundamental problem here is the ldap_groups field in the ldap_auth table. I don't see how the groups can be known ahead of time with either of these configurations. I've tried both of these methods with and without filtering.

aren cambre’s picture

I have to comment: FANTASTIC work on resolving issues!!

I will also test against a Microsoft AD, hopefully in the next few days.

roball’s picture

Yeah - great progress now going on. It seems that currently there are only 2 open issues (#376984: Improving LDAP caching and #324732: Webserver authentication) holding on the next release.

miglius’s picture

Not sure if #324732: Webserver authentication will make it to the release. I see a potential problems if admin user with uid=1 is being authenticated against ldap.

One more issue which I want to include:
#405464: Move functionality from the *config* files to a GUI

roball’s picture

Agreed. Let's keep the webserver auth stuff outside unless the UID 1 problem gets handled as you already do it (very well) in your code.

kassissieh’s picture

Thank you for the improvements and fixes, miglius. I have a feature request: encrypt the anonymous bind password. Thanks.

miglius’s picture

@kassissieh, can you open a separate issue for your request as this issue is more meant for collecting the changes. Also, please be more specific like to encrypt where? In the database? What kind of encryption, etc.

arnd’s picture

Yes great job! It now works mostly fine for me on OpenLDAP (slapd)! But I would be happy, if #400278: Cannot change Common name could also make it into the release. I think, that is quite basic functionality.

miglius’s picture

krisis’s picture

Hi,

I recently installed the alpha2-version and it has the problem of being unable to save the global configuration options because of the switch being based on the text value of the submit buttons. (For the record, I am using the Dutch Translation).

Is there a purposeful reason not to use the id-values (which are unique and static) on the buttons (e.g. edit-submit / edit-reset) to overcome this issue? I looked into the discussion regarding this problem which was closed due to not being able to reproduce so I had a shot at fixing it myself. I changed the #value to #id plus the respective cases and this seems to work nicely. If I knew how to 'patch' something I would submit it :D

#355697: "LDAP UI Options" does not save options

Btw, I am using ldap_auth only on a corporate setup with a Windows 2003 Active Directory so if needed Ill be willing to help test maybe a stable release? (to whatever extend the administrator in question will let me off course).

with regards,

Kristian

chinko’s picture

Hi miglius,

It is great you have resolved many issues lately.

Any plan to release another alpha version soon?

Regards,
Chin

aren cambre’s picture

Just use the dev release. It's really stable.

chinko’s picture

Yes, we have used the dev release for our testing and it is working fine in our environment. None of the unresolved issues affected us.

The first Drupal site in our company is going live very soon. We are a bit uncomfortable using a nightly snapshot build in our production site.

miglius’s picture

Issue tags: +release

There are several open issues I would like to be resolved in this release:
#210023: TLS failure results in an unsecured connection I have uploaded a patch for testing but received no feedback. Thinking of committing that patch anyways.
#417892: ldapgroups "Group by entry" breaks when CN has commas
#324732: Webserver authentication I have no way to test it so not sure about this one either.

Also not sure if following contrib modules are ready to be included in the release:
#396574: LDAPsync component
#353036: LDAP Help Module doesn't show up....
it looks that those modules still are in active development.

kassissieh’s picture

This being my first module, I'm not sure at what point it's ready for release. One issue is that we're not getting the level of community testing required to move the module along. The comment thread suggests that only two people have this running in test or production environments. We're pretty much stuck until more people help out with this.

#396574: LDAPsync component

Richard

johnbarclay’s picture

The help module should not be included. To finish it I need the other parts to be done.

svdoord’s picture

I just tested ldap_integration (version 6.x-1.0-alpha2) in my corporate environment, it works like a charm. I didn't test the optional modules (groups and data), but at least the base functionality works for me.

aren cambre’s picture

alpha2 is very old. You may want to try the latest dev instead.

rschuetzler’s picture

This thread has been quiet for a while now, but still no news of a new release. Is LDAP Integration going to get a new version any time soon?

roball’s picture

In 2 days it is exactly one year after the last alpha release. Maybe this is the time to go for a new alpha ;-)

miglius’s picture

Status: Active » Fixed

A beta1 was released today...

vincetingey’s picture

HURRAY!

roball’s picture

Thanks a lot. Working great!

ajwn’s picture

I to can test successfully allowing all members of a domain access to the site and automatically creating account names based on their user name in AD but when I try to restrict by group I get an error,

"Access denied

* warning: array_intersect() [function.array-intersect]: Argument #1 is not an array in /opt/lampp/htdocs/modules/ldap_integration/ldapgroups.module on line 89.
* Sorry, unrecognized username or password. Have you forgotten your password?

You are not authorized to access this page. "

I have made sure this file ldapgroups.module is read and write, restarted XAMPP, tested with different users and groups. When I log in with the correct password for a user I get the above error but when I log in with an incorrect password I get

"Access denied
Sorry, unrecognized username or password. Have you forgotten your password?
You are not authorized to access this page. "

So it looks like the request from the site is hitting active directory finding an account within the specified group but when accepted not being processed by the LDAP module itself properly..

What can be done aside from making changes to ldapgroups.module?

group syntax is

CN=group,OU=security Group,OU=admin,DC=something,DC=something,DC=com,DC=au

Is this correct as it is not specified with that feature.

Please assist

Thanks.

roball’s picture

You are posting your request into an inappropriate ticket.

ajwn’s picture

My apologies, I am struggling to find how to resolve this, any ideas where I should be going and posting?

roball’s picture

Why not creating an own ticket for it?

johnbarclay’s picture

I was holding off on the help module until the beta was out. Now I can get it working again since LDAP is more stable. I forget if miglius wants it as part of this module distribution or not but we can sort that out later.

I tested the beta on Windows 2008 Server with IIS 7 and Microsoft Active Directory and both ldap authentication and group mapping and filtering worked fine.

Status: Fixed » Closed (fixed)
Issue tags: -release

Automatically closed -- issue fixed for 2 weeks with no activity.