Closed (fixed)
Project:
LDAP integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 Apr 2009 at 19:05 UTC
Updated:
30 Mar 2012 at 18:52 UTC
Jump to comment: Most recent file
Comments
Comment #1
miglius commentedPlease paste here your your exact ldapgroups settings, we need your configuration to troubleshoot.
Comment #2
gettysburger commentedThanks. Here they are.
Comment #3
gettysburger commentedI'm back on this issue trying to get LDAP Groups to work. It worked for me before when they were set externally, but have not worked for me since they went into the admin section.
I have been using the dev from March 30, so I tried the May 9th and have gotten an error:
• warning: ldap_get_option(): supplied argument is not a valid ldap link resource in /srv/www/htdocs/sites/all/modules/ldap_integration/includes/LDAPInterface.inc on line 82.
• warning: ldap_errno(): supplied argument is not a valid ldap link resource in /srv/www/htdocs/sites/all/modules/ldap_integration/includes/LDAPInterface.inc on line 167.
• warning: ldap_error(): supplied argument is not a valid ldap link resource in /srv/www/htdocs/sites/all/modules/ldap_integration/includes/LDAPInterface.inc on line 167.
The third line looks like a typo? ldap_errno()
I also tried uninstalling Persistent Login because I read that people were having trouble with that killing their Groups sync. No luck. Thanks.
Comment #4
gettysburger commentedBTW, my IT guy tells me we are working with a Novell system. Would that make a difference as to which settings I should be using? Thanks.
Comment #5
gettysburger commentedThis was my old ldapgroups.php file that worked just fine:
I am not able to get this to work with the updated internal interface. Any thoughts? Thanks.
Comment #6
miglius commentedldap_errno() is not a typo, but a valid function http://lt.php.net/manual/en/function.ldap-errno.php
It looks like the connection to the LDAP server is not established. Please look at the watchdog messages, they might give some hint. I haven't tried with the Novell though.
Comment #7
gettysburger commentedThanks for the note.
When a new staff member logs in to the site for the first time it grabs their Title, Department, Room Number, Phone Extension, basically everything but their Group. Can it do that without an LDAP connection?
The reports don't show any problems.
The question I have is: when it was working before, when I had the group info in a separate file, it seemed very simple. Now it seems to be asking for a lot more information. My users, in the network, belong to a group called "Staff". I want to map to a role named "Staff". Do you think this is no longer possible with Novell? Thanks.
Comment #8
gettysburger commentedI got it to create a Role based on my Username. That is not what I was trying for, but it may be some progress, nonetheless.
Comment #9
miglius commentedYou configuration is incorrect.
If you use "Group is specified in user's DN", the "Attribute of the DN which contains the group name:" cannot be a CN attribute, since the CN attribute specifies not a group but the user itself. This attribute can be OU or contain other value based on you LDAP setup.
I don't know you setup, but maybe it would be enough just to use the third set of options, "Group by entry". This is used if you have a group entry in the LDAP which lists all the members.
Comment #10
gettysburger commentedI got rid of the first set of options and just used the third. Now no roles are created.
Here is my basic setup. Thanks again for your help.
Comment #11
miglius commentedHow are the groups stored in the LDAP, i.e., a group has a DN and contains all the members, or the each LDAP user has an attribute specifying the group it belongs to or do you want to extract the group from the user's DN?
Comment #12
gettysburger commentedThere are two ways to get the groups:
We're pulling from a novell directory and the net admins have the users grouped by dn. There is only two groups stored this way. Students and everyone else.
Also, there is two cn attributes assigned to each user. The second cn attribute on each user is a more detailed group designator. This is where we get roles such as Staff, Faculty,...etc.
Comment #13
miglius commentedCould you post an example of the user and group DNs or all LDIF entry (with sensitive information changed to *)? that would give an idea how LDAP entries look like.
Comment #14
gettysburger commentedMy admin guy sent me this file in answer to your question. I hope it is what you need. Thanks.
Comment #15
miglius commentedYour LDAP structure is a little wired for me. I looked at "Adjunct Faculty" and this is not a group, but a second CN attribute as well as the Title attribute. I cannot see a LDAP entry for a group "Adjunct Faculty".
Comment #16
gettysburger commentedThanks for the note. My IT guy is off today but I will ask him to explain his 'interesting' setup in the morning.
Comment #17
gettysburger commentedYeah, our Novell guys did not set the system up in any comprehensible way. Nonetheless, that is what I have to work with. Sorry.
The second cn attribute is what I had working before and is what I would like to get working now. Thanks.
Comment #18
gettysburger commentedDoes anyone have any thoughts how I can get this to work? I had it working with the group mappings in an external file. Now that it is in the interface I can not get the setting right. Would anyone that has this working please send me a screen shot of their settings so that i can give it a try.
I have pretty much resolved myself to the fact that this module does not work for mapping groups to roles. I will have to enter the groups/roles manually. I was going to go back to the older version that I had working, but I wish to use the LDAP sync module that I have seen elsewhere. The other parts work and thank you for that.
Comment #19
cgmonroe commentedClearing out old support requests - reopen if problem still exists in newest code