APAR status |
Closed as program error.
| Error description
Environment:
WebSphere Application Server (WAS) 3.5.4
.
Description:Environment:WebSphere Application Server (WAS) 3.5.4.
With WAS security enabled, when using the
com.ibm.CORBA.LocalHost parameter to embed the hostname into
IORs instead of the default IP address of the WAS box, trying
to start the admin console results in no login prompt and an
"Authorization failed for /" message in the tracefile. Any othe
admin client like XMLConfig also results in the same behavior.
.
This same issue exists on version 4.0.1 and 4.0.2. The message
is slightly different, however; "Authorization failed for
/UNAUTHENTICATED".
.
This is resolved in 4.0.3 and the latest security cumulative
eFix applicable to 4.0.2. Description:With WAS security enabled, when using thecom.ibm.CORBA.LocalHost parameter to embed the hostname intoIORs instead of the default IP address of the WAS box, tryingto start the admin console results in no login prompt and an"Authorization failed for /" message in the tracefile. Any otheadmin client like XMLConfig also results in the same behavior..This same issue exists on version 4.0.1 and 4.0.2. The messageis slightly different, however; "Authorization failed for/UNAUTHENTICATED"..This is resolved in 4.0.3 and the latest security cumulativeeFix applicable to 4.0.2. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who *
* set-up com.ibm.CORBA.LocalHost *
* parameter in admin.config. *
****************************************************************
* PROBLEM DESCRIPTION: With WAS security enabled, when using *
* the com.ibm.CORBA.LocalHost = xxxx, *
* adminserver and/or adminconsole can *
* not be started properly, and you also *
* see authorization failed for /. *
****************************************************************
* RECOMMENDATION: Apply efix, or not edit *
* com.ibm.CORBA.LocalHost(using default *
* option). *
****************************************************************
With WAS security enabled, when using
the com.ibm.CORBA.LocalHost parameter, adminserver and/or
adminconsole can not be started properly, and you also see
Authorization failed for / exceptions. Problem conclusion
With WAS security enabled, when using
the com.ibm.CORBA.LocalHost= hostname, the hostname was used
in security tag componnent, but IP address was returned by
IOR, and the inconsistancy cause TaggedSecurityComponnent not
found, thus communication is unsecured. Temporary fix
PQ56074-354.jar Comments
APAR information | APAR number | PQ56074 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-12-18 | Closed date | 2002-01-22 | Last modified date | 2003-01-20 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 | APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels | R350 PSY | UP |
|