PQ67024: DUMPNAMESPACE DOESN'T REQURE CLIENTSAS TO RUN BUT INCLUDES IT INWAS 4.0.X FOR WINDOWS VERSION (NOT IN SOLARIS VERSION) | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Environment: WebSphere Application Server (WAS) 4.0.x for Solaris and Windows . Description: When WAS security is enabled, the dumpNameSpace.bat utility in WAS 4.0.x for Windows requires a login. However, if the %CLIENTSAS% parameter is removed it works. The dumpNameSpace.sh utility in WAS 4.0.x for Solaris doesn't even have the $CLIENTSAS parameter and it works fine whether WAS security is enabled or not. Need to know if this is a security problem or if dumpNameSpace is supposed to be working if WAS security is enabled or not. If it should be working whether WAS security is enabled or not, the %CLIENTSAS% parameter needs to be removed from dumpNameSpace.bat for WAS 4.0.x for Windows.Local fix Remove %CLIENTSAS% from dumpNameSpace.batProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of * * release 4.0.1, 4.0.2, 4.0.3, and 4.0.4, * * who use the dumpNameSpace utility on a * * UNIX platform. * **************************************************************** * PROBLEM DESCRIPTION: dumpNameSpace utility does not prompt * * for user id and password even when * * WAS security is enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** When WAS security is enabled, dumpNameSpace utility should prompt for user id and password first before starting to dump the content of a name space. This is not true on a UNIX system, where the dumpNameSpace utility dumps the name space without asking for user id and password even when WAS security is enabled.Problem conclusion The command option $CLIENTSAS was missing in dumpNameSpace.sh. As a result, the dumpNameSpace utility did not prompt for a user id and password even when WAS security was enabled. The fix for this is to add $CLIENTSAS in dumpNameSpace.sh so that it will pop up a login-on window for a user id and password when WAS security is enabled.Temporary fix Have built and delivered the efix to the customer on 10/10/02Comments
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 #: PQ67024
IBM Group: Software Group
Modified date: Oct 29, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.