URL error for ldap_search

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Attempt to add new ldap group via the admin interface

What is the expected output? What do you see instead?
TemplateSyntaxError at /admin/ldap_groups/ldapgroup/3/
Caught an exception while rendering: Reverse for 'ldap_search' with 
arguments '()' and keyword arguments '{}' not found.

work around it by just hard coding the url as 
"/admin/ldap_groups/ldapgroup/ldap_search/" now searching will work.

Original issue reported on code.google.com by dmbs...@gmail.com on 20 Apr 2010 at 5:46

[GoogleCodeExporter]

The proper solution, as is documented in the README file included in the source 
code, is to add a URL that 
includes the ldap_groups urls.py.

Granted, I do need to update the wiki installation instructions to match the 
README.

Original comment by tphern...@gmail.com on 20 Apr 2010 at 6:53

• Changed state: WontFix

[GoogleCodeExporter]

Ah, Sorry I did easy-install and read the wiki.  I see the other bug I reported 
was 
fixed in the trunk.  I did get everything working well now.

I may submit an enhancement/bug, when looking up membership for a new user it 
seems go 
the entire way down the ldap tree.  Specially for me I have a OU called 
students and 
another called 2010 (and other years all of which are in the OU students).  
Membership 
seems to pick up the only the full 2010 string and not students when I really 
want all 
students to be in a group.  I'm going to play around with it more.

Original comment by dmbs...@gmail.com on 20 Apr 2010 at 7:39

[GoogleCodeExporter]

Yes, I need to both update the wiki and upload a new release to PyPI.  And add 
in some of the fixes in the other issues, add some new features, etc.  I 
haven't had much time to 
maintain the project lately, sadly, and it isn't front-of-mind as it generally 
works for me.

That aside, tell me more about what you are seeing, and what you expect to see. 
 I don't know that LDAP matching will do what I think you want.  If you have 
OU=students,O=rmu 
and OU=2010,OU=students,O=rmu and CN=student1,OU=2010,OU=students,O=rmu and 
also OU=2009,OU=students,O=rmu and more students under that (is that an 
accurate 
description of your schema?), and you want all students to acquire a certain 
Django group, I'm not sure that ldap_groups will do what you need.

The idea behind ldap_groups wasn't to assign a Django group based on the LDAP 
user's DN, but rather assign the Django group based on memberOf attribute.  So, 
if you have an 
LDAP group membership object that contains a bunch of students, and that group 
is part of the student's memberOf attribute, you're all set.  But if you just 
have an OU containing 
students, ldap_groups won't particularly help you.  That I'm aware of, anyway 
-- others may have hacked it to work.

Where I work, our LDAP schema is very deep, very nested, and the actual OU 
structure doesn't at all capture the various permissions groups to which an 
individual belongs.  So we 
went for membership to assign our permissions.

Original comment by tphern...@gmail.com on 20 Apr 2010 at 7:58

[GoogleCodeExporter]

That is about how my ldap is set up.  I just added the students to be a member 
of the 
student group and it works now.

Original comment by dmbs...@gmail.com on 26 Apr 2010 at 7:47