SCOM uses the MID server user to authenticate. Please make sure the MID user has access to SCOM.
If Windows authentication is used by the connector to access the SCOM database (OperationsManagerDW), the MID Server service should be running with a user having read access to the SCOM database. Ensure that the correct credentials are used:
- In the local services, right-click the MID Server service and select Properties.
- In the Log On tab, ensure that This account is selected with the details of the user in the Windows domain having read access to the SCOM database.
Example of error if the user doesn't have access:
Connection test failed: SCOM Event connector failed.
Microsoft.EnterpriseManagement.Common.UnauthorizedAccessEnterpriseManagementException: The user does not have sufficient permission to perform the operation.
System.ServiceModel.Security.SecurityNegotiationException: The caller was not authenticated by the service.
System.ServiceModel.FaultException: The request for security token could not be satisfied because authentication failed.
at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target)
at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState)
- MID server script file: SCOMConnector.groovy (events connector functionality)
- MID server script includes: ScomJS (Metric and BI-Directional functionality)
- MID server script file: Invoke-UpdateAlert.ps1 (Bi-Directional functionality)
This is true only if the SCOM uses the “Windows Authentication” option (otherwise it will use user and password credentials)
Port 5724 should be open from the SCOM server (Configuring a Firewall for Operations Manager — Microsoft docs)