PK93408: INCORRECT USERID AND/OR PASSWORD CAUSES USER ACCOUNT LOCKOUT IN LDAP USER REGISTRY DURING ADDNODE PROCESS.

Fixes are available

APAR status

Closed as program error.

Error description

During addNode processing, multiple SOAP threads end up making
bind calls in a short interval to security code, that causes one
incorrect user login with user being locked out in LDAP user
registry.

Following are the Exceptions in AddNod.log file
-----------------
[xx/xx/xx ] 0000000a SOAPConnector >  invokeTemplate Entry


javax.management.JMRuntimeException:
ADMN0022E: Access is denied for the emitNotification operation
on NotificationService MBean because of insufficient or empty
credentials.
------------------

And Security traces/logs will have following exceptions:

--------------------------------

[xx/xx/xx] 00000041 LdapRegistryI <  checkPassword Exit

javax.naming.AuthenticationException:
[LDAP: error code 49 - 80090308: LdapErr: DSID-0C09030B,
comment:
AcceptSecurityContext error, data 52e, v893

[xx/xx/xx] 00000074 ltpaLoginModu <  login() Exit

javax.naming.AuthenticationException:
[LDAP: error code 49 - 80090308: LdapErr: DSID-0C09030B,
comment:
-------------------------

The multiple threads spawn that make LDAP bind calls will show
that starting with "SOAPConnectio > handleRequest Entry" that
shows incoming SOAP request

Then it will shows "AdminServiceI >  invoke Entry", incoming
SOAP call triggered the server to initiate a call.

Multiple SOAP threads will end up making bind call from
security code, that leads to LDAP user to be locked out.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: Wrong userid or password can cause the  *
*                      user to be locked out                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server allows a client that failed to
login to proceed because many operations can run as
"UNAUTHENTICATED", such as queryNames and isAlive. So a client
will fail only when it reaches a stage where *authorization*
is required. In the example of addNode, before the command
fails as a whole, it has made 6 failed logins which are all
tolerated. So when the command finally fails, it has run
enough failed logins to cause the userid to be locked out by
the user registry at a site where a user registry lock-out
policy (after, say 6, failed logins) is in place.

Problem conclusion

The solution is to allow the user to set a custom property
called "com.ibm.ws.management.connector.loginQuickFail" in the
cell. When this property is set to true, WebSphere will fail a
client immediately when it fails a single login.

The property is set using the administrative console: System
administration
> Cell > Custom Properties > New, then fill in the property
name and value.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.31 and 7.0.0.9.  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
PK93408
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-07
Closed date
2009-11-17
Last modified date
2009-11-17

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK93408: INCORRECT USERID AND/OR PASSWORD CAUSES USER ACCOUNT LOCKOUT IN LDAP USER REGISTRY DURING ADDNODE PROCESS.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?