Tickets :: [#7900] Can't see/add LDAP users in permissions forms

6.0.0-beta1

7/5/25

Summary	Can't see/add LDAP users in permissions forms
Queue	Horde Base
Queue Version	3.3.2
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	kristian.lance (at) crc (dot) ca
Created	01/27/2009 (6003 days ago)
Due
Updated	01/30/2009 (6000 days ago)
Assigned	01/27/2009 (6003 days ago)
Resolved	01/30/2009 (6000 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

01/30/2009 04:30:47 PM	Chuck Hagenbuch	State ⇒ Not A Bug

01/30/2009 04:28:44 PM	kris (at) kayell (dot) com	Comment #8	Reply to this comment
I have resolved this issue by correcting my LDAP config. in the issue mentioned below (http://bugs.horde.org/ticket/7640). Please mark as resolved. [Show Quoted Text - 24 lines][Hide Quoted Text] Correction: the file I modified was ldap.php, not ldap.conf. Coffee time. I have a litte more insight into this problem that might help. I reported the following issue back in November, regarding LDAP authentication not working in Horde 3.3, that seems to have been forgotten: http://bugs.horde.org/ticket/7640 In order to get LDAP authentication working in 3.3 and 3.3.2 I had to make a modification to the code in lib/Horde/Auth/ldap.conf. I'm thinking that this modification allows users to log in, but I'm speculating that there's a chunk of code somewhere else that's attempting to look up the LDAP to get a list of valid users, and failing for the same reason that the login was failing before I 'fixed' it. It's 3.3.2, sorry it was a typo in my message. Okay. You say you upgraded to 3.2.2, but the queue version is set to 3.3.2. Which is it?

01/30/2009 03:35:27 PM	kristian (dot) lance (at) crc (dot) ca	Comment #7	Reply to this comment
Correction: the file I modified was ldap.php, not ldap.conf. Coffee time. [Show Quoted Text - 21 lines][Hide Quoted Text] I have a litte more insight into this problem that might help. I reported the following issue back in November, regarding LDAP authentication not working in Horde 3.3, that seems to have been forgotten: http://bugs.horde.org/ticket/7640 In order to get LDAP authentication working in 3.3 and 3.3.2 I had to make a modification to the code in lib/Horde/Auth/ldap.conf. I'm thinking that this modification allows users to log in, but I'm speculating that there's a chunk of code somewhere else that's attempting to look up the LDAP to get a list of valid users, and failing for the same reason that the login was failing before I 'fixed' it. It's 3.3.2, sorry it was a typo in my message. Okay. You say you upgraded to 3.2.2, but the queue version is set to 3.3.2. Which is it?

01/30/2009 03:33:26 PM	kristian (dot) lance (at) crc (dot) ca	Comment #6	Reply to this comment
I have a litte more insight into this problem that might help. I reported the following issue back in November, regarding LDAP authentication not working in Horde 3.3, that seems to have been forgotten: http://bugs.horde.org/ticket/7640 In order to get LDAP authentication working in 3.3 and 3.3.2 I had to make a modification to the code in lib/Horde/Auth/ldap.conf. I'm thinking that this modification allows users to log in, but I'm speculating that there's a chunk of code somewhere else that's attempting to look up the LDAP to get a list of valid users, and failing for the same reason that the login was failing before I 'fixed' it. It's 3.3.2, sorry it was a typo in my message. Okay. You say you upgraded to 3.2.2, but the queue version is set to 3.3.2. Which is it?

01/29/2009 03:47:07 PM	kristian (dot) lance (at) crc (dot) ca	Comment #5	Reply to this comment
It's 3.3.2, sorry it was a typo in my message. Okay. You say you upgraded to 3.2.2, but the queue version is set to 3.3.2. Which is it?

01/28/2009 02:36:03 AM	Chuck Hagenbuch	Comment #4	Reply to this comment
Okay. You say you upgraded to 3.2.2, but the queue version is set to 3.3.2. Which is it?

01/27/2009 04:13:40 PM	kristian (dot) lance (at) crc (dot) ca	Comment #3 New Attachment: horde-screencap.jpg	Reply to this comment
You're not confused at all, Chuck. That's exactly what I mean. Here's a screen capture. And it doesn't only happen in Horde permissions, I can't assign individual user permissions to calendars in Kronolith either, which I assume uses the same code. I'm confused as to what you mean. In the permission editing screen, you have no option to add individual users? You don't have either a text box or a dropdown?

01/27/2009 03:55:53 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
I'm confused as to what you mean. In the permission editing screen, you have no option to add individual users? You don't have either a text box or a dropdown?

01/27/2009 02:22:27 PM	kristian (dot) lance (at) crc (dot) ca	Comment #1 Priority ⇒ 1. Low State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Base Summary ⇒ Can't see/add LDAP users in permissions forms Type ⇒ Bug	Reply to this comment
I recently upgraded from Horde 3.1.6 to Horde 3.2.2. I use LDAP authentication, so there are no user accounts in Horde for my users. In 3.1.6 I was able to set permissions for individual users by clicking the Individual Users tab in Administer Permissions, and typing their usernames into the box provided. In Horde 3.2.2 I can no longer set permissions for individual LDAP users, i.e. the button to add a user is missing. If, for security reasons, it doesn't let me type usernames in by hand, it should at least look them up on the ldap.