What steps will reproduce the problem?
1. Create LDAPGroup mapping an OU to a Django Group
2. An LDAP user logs in for first time, and is created in Django db.
Permissions are assigned based on LDAP group membership *at that
moment*.
3. The user's group memberships in LDAP change.
4. The user logs in to Django via LDAP after the LDAP group membership
change.
What is the expected output? What do you see instead?
User should acquire appropriate Django Group membership based on new
LDAP group membership. Instead, user retains Django Group
memberships as assigned at user creation.
In short, the app should check the LDAP group memberships every time
the user logs in, and (re-)assign Django Group memberships as
appropriate.
Original issue reported on code.google.com by tphern...@gmail.com on 19 Jan 2010 at 10:48
Original issue reported on code.google.com by
tphern...@gmail.com
on 19 Jan 2010 at 10:48