History: had the 7.x-1 branch installed. After 1 of the updates, the server crashed when a new user tried to authenticate with ldap. I completely uninstalled the ldap module and cleared the database of ldap tables. Installed 7.x-2-beta3 and now I have the following issue.

User name is registered (previous ldap user):

If no Drupal Account Provisioning Options are selected, the user can log in fine.

  1. Edit the user information by changing a value (i.e. firstname)
  2. Check either or both Drupal Account Provisioning Options
  3. Attempt to log in, the server crashes.
  4. If you look at the user information, it has been changed to match what is in Ldap.

User is now unable to log in. When a login is attempted, the site fails to load.

You remove the check from Drupal Account Provisioning Options so no Drupal Account Provisioning Options are checked, you can edit the user, click on save, and the user can then again log in.

For a new user:

If no Drupal Account Provisioning Options are selected, the user gets "Sorry, unrecognized username or password"

  1. Check either or both Drupal Account Provisioning Options
  2. Attempt to log in, the server crashes.
  3. User is not created

Please let me know if you would need any further information to assist in this.

Comments

squ1rr3l’s picture

I've seen this as well. The Apache log (running on Linux) indicates a memory overflow error, or closes the child process with a Segmentation fault (11). Often there is a crash with *** glibc detected *** /usr/sbin/apache2: invalid fastbin entry (free): 0xbfc7b378 *** or similar invalid memory location error.

Looks like there is either a runaway loop or a recursion error.

fbouzek’s picture

Ok, here is the deal. This only happens if I have "Group Audience" field in the Account Settings.

If I remove the "Group Audience" field from the Account Settings, I am able to log in with no issues.

johnbarclay’s picture

I would say this has to do with the ldap authorization og code. Please test against 7.x-2.x-dev. See also #1777088: LDAP Authorization: dangerous iterations using og_load_multiple & og_get_all_group()

fbouzek’s picture

It was tested against 7.x-2.x-dev also. This may be an OG issue. I'll keep this issue posted on my findings. I am going to do a full install from scratch to see what happens. Our site has been in development for over a year now waiting on this module to be released.

fbouzek’s picture

Ok, on a fresh install of Drupal 7.x-18, I install the ldap module, I enable Ldap server, and LDAP User, enter the creds that work in ldap 7.x-1.0-beta12 and I get the following error when I attempt to test the server:

Warning: Invalid argument supplied for foreach() in LdapServer->groupUserMembershipsFromEntry() (line 1594 of /var/www/html/sites/all/modules/ldap/ldap_servers/LdapServer.class.php).
Warning: Invalid argument supplied for foreach() in LdapServer->groupUserMembershipsFromEntry() (line 1594 of /var/www/html/sites/all/modules/ldap/ldap_servers/LdapServer.class.php).

I get the following results:

Binding with DN for non-anonymous search (cn=provisionproxy,ou=Test,o=VEC). Using password stored in configuration
Successfully bound to server

johnbarclay’s picture

Can you try against 7.x-2.x-dev?

fbouzek’s picture

I tried with 7.x-2.x-dev also, same results.

I have opened a new issue for #5: http://drupal.org/node/1882276

fbouzek’s picture

If I add group_audience to the Account Settings, New users cannot log in (via Ldap). Existing Users cannot log in until you go to their profile and hit save (no changes needed).

If I remove group_audience from Account Settings, New users can log in fine and get registered fine, but I cannot assign users to a group. http://drupal.org/node/1038232

I am using OG 7.x-1.x-dev (I tried og 7.x-1.5 first) and LDap 7.x-2.0-dev (I tried 7.x-2.0-beta3 first).

I would update to OG 7.x.2 but I cannot get the migrate to work so upgrading breaks everything.

johnbarclay’s picture

Version: 7.x-2.0-beta3 » 7.x-2.x-dev
fbouzek’s picture

Ok, I have taken the following steps and here are my results:

On a clean server, I created the mysql database
I installed Drupal 7.19
I installed the following modules:

  • Ldap 7.x-2.0-dev
  • Og 7.x-2.0-rc3
  • Entity
  • Views_bulk_operations
  • Entityreference
  • Token
  • Views
  • Ctools
  • Module_filter
  • Realname

The following modules are enabled:
1. Block
2. Chaos Tools
3. Color
4. Comment
5. Contextual links
6. Dashboard
7. Database logging
8. Entity API
9. Entity Reference
10. Entity Tokens
11. Field
12. Field SQL storage
13. Field UI
14. File
15. Filter
16. Help
17. Image
18. Ldap Authentication
19. LDAP Servers
20. LDAP User Module
21. List
22. Menu
23. Node
24. Number
25. Options
26. Organic Groups
27. Organic groups access control
28. Organic groups field access
29. Organic groups UI
30. Path
31. RDF
32. Search
33. Shortcut
34. System
35. Taxonomy
36. Text
37. Token
38. Toolbar
39. Update Manager
40. User
41. Views
42. Views Bulk Operations
43. Views UI

Configure Ldap and was unsuccessful due to error in http://drupal.org/node/1880310
I added the patch from #4 and was able to successfully log in with ldap creds, and account was created.

Go to OG Field settings, set the Bundles to User/user and Fields to Group Audience. save.

Go to edit user and get the following error: (Note: remove the group audience and error goes away.)

Error
The website encountered an unexpected error. Please try again later.
Error message
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'node.entity_id' in 'where clause': SELECT node.nid AS entity_id, node.vid AS revision_id, node.type AS bundle, :entity_type AS entity_type FROM {node} node WHERE (node.nid = :db_condition_placeholder_0) AND(( ( EXISTS (SELECT na.nid AS nid FROM {node_access} na WHERE (( (na.gid = :db_condition_placeholder_1) AND (na.realm = :db_condition_placeholder_2) ))AND (na.grant_view >= :db_condition_placeholder_3) AND (node.entity_id = na.nid) )) AND (node.entity_type = :db_condition_placeholder_4) )OR (node.entity_type <> :db_condition_placeholder_5) ); Array ( [:db_condition_placeholder_0] => -1 [:db_condition_placeholder_1] => 0 [:db_condition_placeholder_2] => all [:db_condition_placeholder_3] => 1 [:db_condition_placeholder_4] => node [:db_condition_placeholder_5] => node [:entity_type] => node ) in EntityFieldQuery->execute() (line 1145 of /var/www/html/includes/entity.inc).

johnbarclay’s picture

Title: Server Crashes after successful Ldap to Drupal sync when Drupal Account Provisioning Options are selected » LDAP User: with OG 7.2 Server Crashes after successful Ldap to Drupal sync with Drupal Account Provisioning Options
johnbarclay’s picture

Status: Active » Postponed (maintainer needs more info)

Do you still have the same issues with a clean install of 7,x-2.0-dev? LDAP Authorization OG was altered quite a bit.

Erik Seifert’s picture

We got the same problem.

Hotfix:
Add a default group to every user

Roman_L’s picture

Issue summary: View changes

Hi and first thanks for this great module,

i configured LDAP module to sync/create a user in LDAP server when a drupal user is created. My user object have a "sn" ldap attribute mapped to a "field_name" drupal field.

I have also Organic Groups (2.8) installed and configured.
It adds an autocomplete filter for group membership in the admin/people/create drupal form ("option in OG : show in register form")

So i am facing a strange behavior when creating a new user :

- if i create the user without filling the og group membership form : all is ok, the user is created in LDAP;

- if i create the user filling the og group membership form, the user creation fails with an LDAP object class violation error; looking at the logs, the "sn" attribute is empty/lost !

If someone could explain me why filling the og form makes me loose the "sn" attribute ? ...or how to avoid this ?

grahl’s picture

Status: Postponed (maintainer needs more info) » Active
grahl’s picture

Component: Miscellaneous » Code
Status: Active » Closed (outdated)

I am not able to reproduce the problem and since the ticket is as old as it is without further details, I'm closing this ticket.

Please feel free to open a new ticket if you are still affected and can shed some more light on the context of how to reproduce this.