PQ60862: WAS 4.0.2 EXPECTS CONFIG FILE TO BE SPECIFIED IN TRUSTEDSERVERS.PROPERTIES EVEN IF THE TA INTERCEPTOR DOES NOT HAVE ADD PROPS

APAR status
Closed as program error.

Error description
In WAS 4.0.2 It seems like the trust Association properties are
stored in WCCM. IN earlier version i.e 3.5.X the
trustedservers.properties was stored in a config file.
Local fix
There is no need to store the Trust Association properties in
WCCM, so we will continue to read the properies from
trustedservers.properties file as we were doing in ASV356
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users       *
*                 implementing a Trust Association Interceptor *
*                 and not subclassing                          *
*                 WebSphereBaseTrustAssociationInterceptor     *
*                 and implementing the init() function.        *
****************************************************************
* PROBLEM DESCRIPTION: WAS4.0.2 expects Config file to be      *
*                      specified in trustedServers.properties  *
*                      even though the TAI does not have any   *
*                      additional properties.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem is that only those Trust Association Interceptors
that have additional properties need to specify an additional
file in trustedservers.properties. In WAS 4.0.2 the Trust
Association properties are stored in WCCM. This was done in
such a way that it became necessary to specify an additional
file even though the TAI did not have any additional properties
to specify. In earlier versions i.e 3.5.X all the properties
for Trust Association were read from a file.
Problem conclusion
There is no need to store the Trust Association properties in
WCCM. The problem has been resolved by reading the Trust
Association properties from a file exactly the same mannor
as WebSphere 3.5.6.
Temporary fix
PQ60862_test.jar
Comments
APAR information
APAR number PQ60862
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-05-06
Closed date 2002-05-29
Last modified date 2002-06-27

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
SECURITY          

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ60862
IBM Group: Software Group
Modified date: Jun 27, 2002