| Request | LDAPMultiPlugins -- bug report -- by Wichert Akkerman |
| Posted on | Sep 25, 2007 10:43 am |
| Subscribe |
| Resolve by Jens Vagelpohl on Jul 23, 2008 3:40 pm | |
|
Closing due to lack of followup. If the problem still exists just let me know, I can't test this myself. |
|
|
|
| Comment by Jens Vagelpohl on May 30, 2008 6:19 pm | |
|
Wichert, if you're still having issues cold you take a look at these changes in LDAPUserFolder and LDAPMultiPlugins? http://svn.dataflake.org/viewvc?view=rev&revision=1480 http://svn.dataflake.org/viewvc?view=rev&revision=1481 You need to make sure to test the current trunk for both packages together. I'm hoping this will solve at least some of the objectGUID handling issues. I can't really test it because I don't have a suitable AD environment to work with. |
|
|
|
| Initial Request by Wichert Akkerman on Sep 25, 2007 10:43 am | |
|
Still tracking down while LDAP groups are not working properly with LDAPMultiPlugins I found the following: when trying search for a group based on its id (which will be the objectGUID) ActiveDirectoryMultiPlugin.enumerateGroups builds an LDAP search filter which is passed to LDAPDelegate.search(). The first thing that happens there is filter=to_utf8(filter). At that point the binary objectGUID is mangled and the search will fail. I'm not sure how we can fix this. The options I can see are to move the utf-8 conversion higher up in the stack or modify LDAPDelegate.search to look for binary attributes and not pass those to utf-8. Both are non-trivial. |
