PQ43251: WASSECK CUSTOM LOGIN W/ WAS 3.5 FAILS AUTHENTICATION, RETURNS TOLOGIN PAGE


APAR

APAR status
Closed as user error.

Error description
Implemented Custom Login in WEbSphere 3.5 and 3.5.2 on Win NT 4.
0 using SecureWay ldap server.  In both cases Basic Challenge wo
rks but Custom Login fails.  TRaces indicate that authentication
 is failing although user id is valid.  Trace files have been cr
eated and will be placed in WASDOC0 under APARS/pq43251.zip
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
hostname e.g. xxx.austin.ibm.com because the domain name
specified for SSO is austin.ibm.com. This is how it is designed.
APAR information
APAR numberPQ43251
Reported component nameWAS STANDARD NT
Reported component ID5648C8301
Reported release350
StatusCLOSED USE
PENoPE
HIPERNoHIPER
Submitted date2000-11-08
Closed date2001-01-31
Last modified date2001-01-31

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
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ43251
IBM Group: Software Group
Modified date: 2001-01-31