PI09741: SEEING MANY FAILED LOGINS IN SECURITY AUDIT LOG AFTER TURNING ON THE AUDIT LOGGING.

Fixes are available

APAR status

Closed as program error.

Error description

The following bogus unsuccessful authentication events were
logged in security audit log files:

Seq = 65424 | Event Type = SECURITY_AUTHN | Outcome =
UNSUCCESSFUL | OutcomeReason = DENIED | OutcomeReasonCode = 1 |
SessionId = 0 | RemoteHost = myHost.myComp.com | RemoteAddr =
null | RemotePort = 47475 | ProgName = WebSphere | Action =
resolve_complete_info | AppUserName = null | ResourceName =
resolve_complete_info | RegistryUserName = null |
AccessDecision = denied | ResourceType = ORB
| ResourceUniqueId = 0 | PermissionsChecked = null |
PermissionsGranted = null | RolesChecked = null | RolesGranted
= null | CreationTime = Mon Dec 16 09:55:30 CST 2013 |
GlobalInstanceId = 0 | EventTrailId = null |
FirstCaller = null | Realm = myRealm:389 | RegistryType = LDAP
| AuthnType = challengeResponse | Provider = IBMCSI |
ProviderStatus = true

The WebSphere server process and applications ran normally.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server.                                     *
****************************************************************
* PROBLEM DESCRIPTION: Bogus unsuccessful authentication       *
*                      events were logged in security audit    *
*                      log files.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following bogus unsuccessful authentication events were
logged in security audit log files:
Seq = 65424 | Event Type = SECURITY_AUTHN | Outcome =
UNSUCCESSFUL | OutcomeReason = DENIED | OutcomeReasonCode = 1
| SessionId = 0 | RemoteHost = myHost.myComp.com | RemoteAddr
= null | RemotePort = 47475 | ProgName = WebSphere | Action =
resolve_complete_info | AppUserName = null | ResourceName =
resolve_complete_info | RegistryUserName = null |
AccessDecision = denied | ResourceType = ORB |
ResourceUniqueId = 0 | PermissionsChecked = null |
PermissionsGranted = null | RolesChecked = null | RolesGranted
= null | CreationTime = Mon Dec 16 09:55:30 CST 2013 |
GlobalInstanceId = 0 | EventTrailId = null | FirstCaller =
null | Realm = myRealm:389 | RegistryType = LDAP | AuthnType =
challengeResponse | Provider = IBMCSI | ProviderStatus = true
The WebSphere server process and applications ran normally.

Problem conclusion

When the flow of a request/reply sequence through the ORB is
intercepted at the server side, if there's no security
information, and client authentication is not required, no
unsuccessful authentication event should be written to security
audit log.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.33, 8.0.0.9, and 8.5.5.3.  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
PI09741
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-16
Closed date
2014-02-28
Last modified date
2014-05-20

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

R700 PSY
UP
R800 PSY
UP
R850 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI09741: SEEING MANY FAILED LOGINS IN SECURITY AUDIT LOG AFTER TURNING ON THE AUDIT LOGGING.

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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?