Bug 793387 (JBEPP-468) - Administration portlets not accessible when reconnection to LDAP from another instance
Summary: Administration portlets not accessible when reconnection to LDAP from another...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-468
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.0.1.CR01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.1.GA
Assignee: mposolda
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-17 10:39 UTC by Viliam Rockai
Modified: 2015-09-01 03:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-21 15:18:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-468 0 Major Closed Administration portlets not accessible when reconnection to LDAP from another instance 2012-11-15 00:40:23 UTC

Description Viliam Rockai 2010-09-17 10:39:15 UTC
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008yXf1
project_key: JBEPP

I'm unable to access admin portlets in EPP (i.e. create new user portlet) after these steps:

1. Start EPP 5.0.1 with some LDAP configured (rw access) ... shut it down after initialization 
1. Start another clean instance of EPP 5.0.1 with the same LDAP configured (rw access) ... shut it down after initialization 

this is the exception thrown:
12:23:07,048 ERROR [PortletApplicationController] Error while rendering the porlet
org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=1,line=24],data=	boolean userCouldEditPage = uicomponent.hasEditPermissionOnPage();] for template app:/groovy/admintoolbar/webui/component/UIAdminToolbarPortlet.gtmpl
	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:162)
	at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:105)
	at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:112)
	at org.exoplatform.groovyscript.text.TemplateService.merge(TemplateService.java:117)
	at org.exoplatform.webui.core.lifecycle.Lifecycle.renderTemplate(Lifecycle.java:132)
	at org.exoplatform.webui.core.lifecycle.Lifecycle.processRender(Lifecycle.java:85)

Comment 1 Jared MORGAN 2011-11-18 01:02:42 UTC
Release Notes Docs Status: Added: Not Required


Comment 2 Takayuki Konishi 2011-12-05 08:58:50 UTC
Forum Reference: Added: https://na7.salesforce.com/500A0000008yXf1


Comment 4 Takayuki Konishi 2011-12-07 06:01:02 UTC
Help Desk Ticket Reference: Added: https://na7.salesforce.com/500A0000008yXf1
Forum Reference: Removed: https://na7.salesforce.com/500A0000008yXf1 


Comment 5 hfnukal@redhat.com 2012-01-10 10:20:10 UTC
Labels: Added: EPP_5_2_1_Candidate


Comment 6 boleslaw.dawidowicz 2012-02-16 09:18:01 UTC
Labels: Removed: EPP_5_2_1_Candidate 


Comment 7 mposolda 2012-02-21 15:18:45 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Release Notes Docs Status: Not Yet Documented

Release Notes Text: 
CAUSE: This is an issue for EPP 5.0.1 and EPP 5.1 but it can't be reproduced in EPP 5.2 and so it's not issue anymore.

It's caused by the fact, that groups, which were mapped to LDAP (like /platform/administrators or /platform/users) were already in LDAP when portal was executed for the first time, which means that OrganizationDatabaseInitializer couldn't create these groups and also group navigations for these groups.

So group navigations were created by NewPortalConfigListener, but there was a bug in NewPortalConfigListener (or bad default configuration) which caused that Group configurations were created with access_permission=null and edit_permissions=null. That causes NullPointerException thrown from UIAdminToolbarPortlet UI component when user wants to access page for Group navigation of some LDAP group (like ApplicationRegistry or OrganizationManagement page)

FIX: In EPP 5.2 is Group initialization part in NewPortalConfigListener rewritten, which means that groups are correctly initialized with all the fields properly assigned.

Comment 8 mposolda 2012-03-22 19:35:20 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,6 +1,3 @@
-Release Notes Docs Status: Not Yet Documented
-
-Release Notes Text: 
 CAUSE: This is an issue for EPP 5.0.1 and EPP 5.1 but it can't be reproduced in EPP 5.2 and so it's not issue anymore.
 
 It's caused by the fact, that groups, which were mapped to LDAP (like /platform/administrators or /platform/users) were already in LDAP when portal was executed for the first time, which means that OrganizationDatabaseInitializer couldn't create these groups and also group navigations for these groups.

Comment 10 Jared MORGAN 2012-03-23 01:46:44 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1 @@
-CAUSE: This is an issue for EPP 5.0.1 and EPP 5.1 but it can't be reproduced in EPP 5.2 and so it's not issue anymore.
+A problem with the logic in OrganizationDatabaseInitializer caused issues with LDAP group mapping and permissions when the platform was executed for the first time. The fix introduces updated logic in NewPortalConfigListener, which ensures LDAP groups are correctly initialized, with all permission fields properly assigned.-
-It's caused by the fact, that groups, which were mapped to LDAP (like /platform/administrators or /platform/users) were already in LDAP when portal was executed for the first time, which means that OrganizationDatabaseInitializer couldn't create these groups and also group navigations for these groups.
-
-So group navigations were created by NewPortalConfigListener, but there was a bug in NewPortalConfigListener (or bad default configuration) which caused that Group configurations were created with access_permission=null and edit_permissions=null. That causes NullPointerException thrown from UIAdminToolbarPortlet UI component when user wants to access page for Group navigation of some LDAP group (like ApplicationRegistry or OrganizationManagement page)
-
-FIX: In EPP 5.2 is Group initialization part in NewPortalConfigListener rewritten, which means that groups are correctly initialized with all the fields properly assigned.


Note You need to log in before you can comment on or make changes to this bug.