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 fixProblem summaryProblem conclusionTemporary fixComments
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 number | PQ43251 | Reported component name | WAS STANDARD NT | Reported component ID | 5648C8301 | Reported release | 350 | Status | CLOSED USE | PE | NoPE | HIPER | NoHIPER | Submitted date | 2000-11-08 | Closed date | 2001-01-31 | Last modified date | 2001-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 APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|
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
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|