Bug 794070 (JBEPP-1137)

Summary:	Unable to remove DB users if LDAP store is not read-only
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	Portal	Assignee:	Boleslaw Dawidowicz <bdawidow>
Status:	VERIFIED ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.GA, 5.1.1.GA	CC:	mputz, theute
Target Milestone:	---	Keywords:	Reopened
Target Release:	5.2.1.ER02
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-1137
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	It was discovered that an error in the PicketLink IDM caused a problem with removing an LDAP User from a read/write user store, when the user was not present in the IDM database. The fix introduces logic improvements to user management that ensures a user can only be removed from the correct identity store.	Story Points:	---
Clone Of:		Environment:	- EPP configured with LDAP using picketlink-idm/examples/picketlink-idm-ldap-acme-config.xml - FallbackIdentityStoreRepository option: readOnly=false
Last Closed:	2012-02-29 20:54:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Martin Weiler 2011-08-30 11:21:31 UTC

Help Desk Ticket Reference: https://na7.salesforce.com/500A0000007qhQq
project_key: JBEPP

Trying to delete one of the default DB users (john, mary...) in a setup with LDAP (readOnly=false) fails with the following error:

ERROR [portal:UIPortalApplication] Error during the processAction phase
java.lang.NullPointerException
	at org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.removeIdentityObject(LDAPIdentityStoreImpl.java:498)
	at org.picketlink.idm.impl.repository.FallbackIdentityStoreRepository.removeIdentityObject(FallbackIdentityStoreRepository.java:490)
	at org.picketlink.idm.impl.api.session.managers.PersistenceManagerImpl.removeUser(PersistenceManagerImpl.java:231)
	at org.exoplatform.services.organization.idm.UserDAOImpl.removeUser(UserDAOImpl.java:251)
	at org.exoplatform.organization.webui.component.UIListUsers$DeleteUserActionListener.execute(UIListUsers.java:210)

Comment 2 Jared MORGAN 2011-11-16 03:10:51 UTC

Release Notes Docs Status: Added: Not Yet Documented

Comment 3 hfnukal@redhat.com 2012-01-13 11:44:46 UTC

Labels: Added: EPP_5_2_1_Candidate

Comment 4 Thomas Heute 2012-01-13 14:05:06 UTC

Labels: Removed: EPP_5_2_1_Candidate

Comment 5 Boleslaw Dawidowicz 2012-02-29 20:27:02 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:
CAUSE: Due to error in PicketLink IDM it was trying to remove user in store where it was not present

FIX: Code and logic was corrected to remove user only in proper identity store

Comment 6 Boleslaw Dawidowicz 2012-02-29 20:41:31 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,3 +1,3 @@
 CAUSE: Due to error in PicketLink IDM it was trying to remove user in store where it was not present
 
-FIX: Code and logic was corrected to remove user only in proper identity store+FIX: Code and logic was corrected to remove user only in proper identity store (https://issues.jboss.org/browse/PLIDM-36)

Comment 7 Boleslaw Dawidowicz 2012-02-29 20:42:44 UTC

Fixed with update to PicketLink IDM 1.3.1.CR01

Comment 8 Jared MORGAN 2012-03-27 21:31:15 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,3 +1 @@
-CAUSE: Due to error in PicketLink IDM it was trying to remove user in store where it was not present
+It was discovered that an error in the PicketLink IDM caused a problem with  removing an LDAP User from a read/write user store, when the user was not present in the IDM database. The fix introduces logic improvements to user management that ensures a user can only be removed from the correct identity store.-
-FIX: Code and logic was corrected to remove user only in proper identity store (https://issues.jboss.org/browse/PLIDM-36)