bopauth_nxd.exe causing audit failures in Windows Event Log

Products

• CA Service Desk Manager

Issue/Introduction

bopauth_nxd.exe causing audit failures on the background server consistently on requests coming from application servers. 

Seeing below error in Event Viewer --> Security --> Login Failure often in the logs (bopauth_nxd.exe). 

An account failed to log on.

Subject:
Security ID: SYSTEM
Account Name: XXXXX
Account Domain: DOMAIN1
Logon ID: 0x3E7

Logon Type: 4

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: ServiceDesk
Account Domain: SDM-SERVER1

Failure Information:
Failure Reason: The user has not been granted the requested logon type at this machine.
Status: 0xC000015B
Sub Status: 0x0

Process Information:
Caller Process ID: 0x1694
Caller Process Name: D:\PROGRA~1\CA\SERVIC~1\bin\bopauth_nxd.exe

Network Information:
Workstation Name: SDM-SERVER1
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

 

Sample message in Windows Audit Logs:

Environment

CA Service Desk - 17.x

Cause

Entries of interest are highlighted in yellow and bold in the above event log sample.

User "ServiceDesk" is having NTLM login issues.  When the "ServiceDesk" user interacts with the bopauth_nxd.exe process, Windows perceives an issue with the user not having sufficient rights to login to the local server, Workstation "SDM-SERVER1". 

Resolution

The issue is a Windows configuration issue with user permissions.

To address, one would need to grant user "ServiceDesk" appropriate NTLM login rights, usually "allow logon locally" and "logon as a batch" privileges under "Local Policies" for server SDM-SERVER1, especially if a domain account is involved.

Additionally, for web services concerns, the current functionality of SDM Web Services relies on the backend Windows API call for LOGON32_LOGON_INTERACTIVE.  When this API is being leveraged, the login attempt will trip up an Audit error message in the Windows Event Logs, which we have no control over.  You will need to consult with your admin and security teams to determine what is causing the Audit error message to present whenever the LOGON32_LOGON_INTERACTIVE API is being invoked.