Summary: | Group affiliation not always loaded correctly | ||
---|---|---|---|
Product: | Lenya | Reporter: | Andreas Hartmann <andreas> |
Component: | Access Control | Assignee: | Lenya Developers <dev> |
Status: | NEW --- | ||
Severity: | critical | ||
Priority: | P2 | ||
Version: | 1.2.5 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | Other | ||
OS: | other | ||
Attachments: | Initialize user and IP range managers when Group.getMembers() is called. |
Description
Andreas Hartmann
2007-12-06 08:25:01 UTC
Fixed in revision 601779 in the Shibboleth integration branch. Needs to be applied to the 1.2.x branch and to the trunk as well. Created attachment 21239 [details]
Initialize user and IP range managers when Group.getMembers() is called.
This patch does not fix the problem in trunk. If it is applied to trunk, it somehow is preventing the groups from being added to the user, causing them not to be able to login at all. I know that this has hit occasionally at the place I used to work. The only way around it is to restart Tomcat and hope it doesn't happen to a different publication. (In reply to comment #3) An other workaround is to add a new user at the filesystem level . You can copy a [USER].iml file to the config/access-control/passwd folder of the publication, login with this username and assign the missing groups to the existing users. Assigning the groups to the existing users works only in lenya 2.x, but in lenya 1.2.x you can work with the new user until the system is restarted. |