SCCM Connector

Surface Command Connectors
1

We are running the Rapid7 Microsoft SCCM connector microsoft.sccm.app version 1.23.2431.

SCCM AdminService works from a domain-joined Windows device using the same service account and returns data from /AdminService/wmi/SMS_Site and /AdminService/wmi/SMS_SummarizerSiteStatus.

apid7 fails with 401 Client Error: NTLM authentication rejected, which indicates the connector is attempting NTLM or falling back to NTLM.

Does this Surface Command SCCM connector support Kerberos/Negotiate authentication to SCCM AdminService? If yes, what username format and orchestrator configuration are required? If no, this connector is not compatible with SCCM environments where AdminService rejects NTLM.

1 Like
2

Hello, I am getting the same error as you.

Were you able to find a way to make it work ?

3

The current version of our SCCM connector does not yet support Kerberos authentication. We are working on enabling this connector to support Kerberos authentication. That work is queued up behind related architectural enhancements that we first need to make to the InsightConnect’s “Orchestrator”. While we don’t have a firm timeline on the availability of the new version of the SCCM connector, we hope to have it before the end of the year.