-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.1
-
None
-
Confluence 3.1, Java 1.6.0_05, CentOS 5.3, SQL Server 2005, Active Directory LDAP integration
We had an interesting problem where padlock link for editing page permissions in view page mode ended working. After digging around we could narrow it down to this:
- Database contained group that was saved incorrectly by Confluence as "Me & amp; My Team" (without amp space) instead of correct version "Me & My Team"
- This was probably created by earlier version of Confluence, 3.0.2 most likely
- Cannot reproduce creation of incorrect name in database with version 3.1
- PermittedUserFinder.checkGroupExplicitlyPermitted threw NullPointerException which was probably caused by null group as our AD does not contain group with & amp;
Because of this problem padlock didn't open any dialog and there were errors in our log:
2010-01-04 15:13:09,824 ERROR [http-8443-15] [atlassian.confluence.servlet.ConfluenceServletDispatcher] sendError Could not execute action
-- url: /pages/getpagepermissions.action | userName: myusername
java.lang.NullPointerException
at com.atlassian.confluence.user.PermittedUserFinder.checkGroupExplicitlyPermitted(PermittedUserFinder.java:51)
at com.atlassian.confluence.user.PermittedUserFinder.makeResult(PermittedUserFinder.java:43)
at com.atlassian.confluence.pages.actions.GetPagePermissionsAction.execute(GetPagePermissionsAction.java:84)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:168)
at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:35)
at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
- is duplicated by
-
-
- Closed
-