PQ67679: WASSEC - ADDS TAI CAPABILITY TO PQ63020 | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer installed Websphere PTF4 to WAS 4.03. Found out that function fixed by previous efix PQ63020 was unavailable. The cause of the failure appears to be TAI.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server security * * users who use programmatic security with * * Trust Association and Custom Registry. * **************************************************************** * PROBLEM DESCRIPTION: Wehn using a custom registry with * * trust association, the API * * getRemoteUser() returns display name * * rather than security name. * **************************************************************** * RECOMMENDATION: Apply this eFix, or use the display name * * as the same as the security name. * **************************************************************** When using a Custom Registry implementation, security returns the user's display name for getRemoteUser() and getPrincipalName() instead of the user's security name.Problem conclusion If getRemoteUser() and getPrincipalName() are required to return the user's security name, a system property has been added to enable this. com.ibm.ejs.security.customregistry.useSecurityName=trueTemporary fix testing eFix providedComments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67679
IBM Group: Software Group
Modified date: Oct 31, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.