APAR status
Closed as program error.
Error description
Impersonation is not working properly in a clustered. environment. The following steps lead to the failure: a. Admin logs into the web server of a two node cluster. b. Admin invokes custom portlet. Custom portlet allows a search for users. Admin selects the user from the list and clicks "begin impersonating user" or similar. c. Admin successfully impersonates a user, i.e. "testuser". d. Custom logic is invoked that displays "welcome username". This consistently shows the correct impersonated username. e. In some cases, namely a two-node cluster scenario, when a user is being impersonated and a call is made to the method isUserImpersonated(), the method may return false indicating the user is NOT being impersonated when instead the method call should return true indicating the user is currently being impersonated. Notes: - A single-node cluster works 100% of the time. - A standalone node works 100% of the time. - A single-node up in the two-node cluster (with the second node down) works 100% of the time.
Local fix
None available
Problem summary
Impersonation is not working properly in a clustered environment. The following steps lead to the failure: 1. Admin logs into the web server of a two node cluster. 2. Admin invokes custom portlet. Custom portlet allows a search for users. Admin selects the user from the list and clicks "begin impersonating user" or similar. 3. Admin successfully impersonates a user, i.e. "testuser". 4. Custom logic is invoked that displays "welcome username". This consistently shows the correct impersonated username. 5. In some cases, namely a two-node cluster scenario, when a user is being impersonated and a call is made to the method isUserImpersonated(), the method may return false indicating the user is NOT being impersonated when instead the method call should return true indicating the user is currently being impersonated. Notes: - A single-node cluster works 100% of the time. - A standalone node works 100% of the time. - A single-node up in the two-node cluster (with the second node down) works 100% of the time.
Problem conclusion
Moved class holding the original user credentials to a library accessible by the WebSphere Application Server. Manual Steps: Run configuration task "ConfigEngine.[sh|bat] apply-PM34927". Platform Specific: This fix applies to all platforms. PM34927 is part of Cumulative Fix 14 - available on Fix Central. A code fix for this issue is integrated into Cumulative Fix 14 - available from Fix Central: Portal 6.1.0.3 / 6.1.5.0: http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde r?apar=PM37550&productid=WebSphere%20Portal&brandid=5 Portal 6.1.0.4 / 6.1.5.1: http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde r?apar=PM37563&productid=WebSphere%20Portal&brandid=5 Portal 6.1.0.5 / 6.1.5.2: http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde r?apar=PM37648&productid=WebSphere%20Portal&brandid=5 You may need to type or paste the complete address into your Web browser.
Temporary fix
Comments
APAR Information
APAR number
PM34927
Reported component name
WEBSPHERE PORTA
Reported component ID
5724E7600
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-16
Closed date
2011-06-21
Last modified date
2011-06-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE PORTA
Fixed component ID
5724E7600
Applicable component levels
R610 PSY
UP
R615 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.1","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]
Document Information
Modified date:
21 December 2021