Bug 795856

Summary: The result of failed LDAP query should not be cached
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: bkramer <bkramer>
Component: PortalAssignee: Boleslaw Dawidowicz <bdawidow>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.2.1.GACC: epp-bugs, hfnukal
Target Milestone: ---   
Target Release: 5.2.2.ER01   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 10:58:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 830081    
Bug Blocks:    

Description bkramer 2012-02-21 16:35:05 UTC
Description of problem:

Currently, it can happen that if finalResults object (in LDAPIdentityStoreImpl.java) was first initialized inside of try{} block and then Exception happened during LDAP query, it could result in storing such failed result. 

Code in LDAPIdentityStoreImpl.java should be improved to include additional logging and make sure that nothing gets cached in case when LDAP query fails.


Version-Release number of selected component (if applicable):


How reproducible:

** It's not easy to reproduce, but when it happens, it's always in clustered environment.

Comment 1 hfnukal@redhat.com 2012-06-06 11:22:56 UTC
Upgrade Picketlink to at least 1.1.10

Comment 2 Boleslaw Dawidowicz 2012-06-20 10:58:30 UTC
This issue is hard to reproduce and verify however it is likely to assume that PicketLink IDM 1.1.10 upgrade fixes it.