Fixes are available
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
There are a number of user with disabled accounts, ie passwd ?l <username> If such a user tries to login then WebSphere application server crashes. Details from advanced debug for example user., one unusual NULL value appeared against others log native_stdout.log entries. Time: [0x5a01ae97], Process: [25367], Thread: [0xef09b700]: > entering: [UnixRegistryImpl_checkPassword] Time: [0x5a01ae97], Process: [25367], Thread: [0xef09b700]: UnixRegistryImpl_checkPassword: entry: kmko04x, 7, xxxxxxxxxxxx, 11 Time: [0x5a01ae97], Process: [25367], Thread: [0xef09b700]: NATV: epass is (null) Time: [0x5a01ae97], Process: [25367], Thread: [0xef09b700]: NATV: password is xxxxxxxxxxxx Time: [0x5a01ae97], Process: [25367], Thread: [0xef09b700]: NATV: password from its struct is !!xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxx/
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * on Redhat Linux 7 * **************************************************************** * PROBLEM DESCRIPTION: WebSphere crashes when a user with * * disabled account logs in * **************************************************************** * RECOMMENDATION: * **************************************************************** Starting with Redhat Linux 7, WebSphere's local OS registry access null object when a user with disabled account logs in.
Problem conclusion
A null check has been added to the code. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.14 and 9.0.0.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI90068
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-09
Closed date
2017-12-14
Last modified date
2017-12-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022