"Use Integrated Authentication" is unchecked automatically on the associated data source when a Service Graph Connector for SCCM scheduled import runs.Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When running a scheduled import for the Service Graph Connector for SCCM, the import fails with a login error even though the data source connects successfully when tested manually. The 'Use Integrated Authentication' flag on the data source is automatically reset to unchecked each time the scheduled import runs. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Scheduled import for an SGC-SCCM data source fails with the following error in the import log: 2026-03-19 10:33:14 (455) worker.7 worker.7 txid=713294a09377 ImportLog SEVERE *** ERROR *** MID Server reported error: SQLState: null java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user '<domain>\<username>'. ClientConnectionId:6ee4ff61-15cc-4860-9b08-6dfbbf1397b2 com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262) com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:283) com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:129) com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37) com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:5067) com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3731) com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:94) com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3675) com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7194) com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2979) com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2488) com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2142) com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1993) com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1164) com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:760) java.sql/java.sql.DriverManager.getConnection(DriverManager.java:681) java.sql/java.sql.DriverManager.getConnection(DriverManager.java:190) com.service_now.mid.connections.jdbc.JDBCConnection.establishConnection(JDBCConnection.java:149) com.service_now.mid.connections.jdbc.JDBCConnection.lambda$connect$0(JDBCConnection.java:110) com.glide.util.LogContext$Frame.run(LogContext.java:212) com.service_now.mid.connections.jdbc.JDBCConnection.connect(JDBCConnection.java:108) com.service_now.mid.connections.jdbc.JDBCConnectionFactory.create(JDBCConnectionFactory.java:75) com.service_now.mid.connections.ConnectionCachePool.getAvailableConnection(ConnectionCachePool.java:85) com.service_now.mid.connections.ConnectionCache.get(ConnectionCache.java:111) com.service_now.mid.probe.JDBCProbe.getJDBCConnection(JDBCProbe.java:963) com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:228) com.service_now.mid.probe.AProbe.process(AProbe.java:160) com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:138) com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20) com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:643) java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) java.base/java.lang.Thread.run(Thread.java:840) at com.service_now.mid.probe.JDBCProbe.getJDBCConnection(JDBCProbe.java:967) at com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:228) at com.service_now.mid.probe.AProbe.process(AProbe.java:160) at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:138) at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20) at com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:643) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:840) 2026-03-19 10:33:14 (434) worker.7 worker.7 txid=713294a09377 ImportLog Got response from MID server 2026-03-19 10:33:09 (909) glide.memory.watcher SYSTEM GlideLogLogger txid=713294a09377, URL= JOB: BackgroundProgressJob, THREAD= glide.scheduler.worker.7, FG= false, TYPE= 4, STATE= 11, USER= XXXXXX, TIME= 641, JVM= { spCount=1, spTime=359, ttsp=0, appTime=1316 }, MEM= 16, ATTRIBUTES= {} 2026-03-19 10:33:09 (414) worker.7 worker.7 txid=713294a09377 ImportLog Waiting for MID server to respond (0 of 300 secs) Manually testing the same data source succeeds without errorThe Use Integrated Authentication checkbox on the data source is unchecked after each scheduled import run, even if it was manually re-enabled beforehand Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases of the SGC-SCCM plugin currently available. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } - When a scheduled import runs for an SGC-SCCM data source, the prescript invokes SCCMMultiDataSourceUtil.updateDatasource(), which calls _setConnectionDetails(). This method calls _isIntegratedAuth() to determine whether to set the 'Use Integrated Authentication' field on the data source to true or false. - The _isIntegratedAuth() function evaluates three conditions in sequence: Read access — Verifies that the scheduled import's Run As user has read access to the sys_alias table. This check typically passes when the Run As user has admin or equivalent privileges.Alias match — Verifies whether the connection alias on the data source is the default OOB integrated authentication alias. A custom alias will not match this check.Parent alias — Verifies whether the custom connection alias has its Parent field set to the default OOB integrated authentication alias (SCCM JDBC Conn Cred (Integrated Auth)). - If none of these checks return true, the function returns false and the 'Use Integrated Authentication' field is set to false on every scheduled import run. When the Parent field on the connection alias is not populated with the correct OOB alias record, the third check fails, integrated authentication is disabled at runtime, and the MID Server attempts to authenticate using SQL credentials instead, which the database rejects. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Before making changes, it is recommended to test in a development or sub-production instance first. 1. Navigate to **Service Graph Connectors > SCCM > Connection Aliases** (or navigate directly to the 'sys_alias' table scoped to the SCCM integration application). 2. Open the custom connection alias used by the failing scheduled import. 3. Locate the **Parent** field on the connection alias record. 4. Set the **Parent** field to the default OOB SCCM integrated authentication alias: **SCCM JDBC Conn Cred (Integrated Auth)** or the correct alias that has the right details configured ↳ The parent-child relationship in the `sys_alias` table is what the `_isIntegratedAuth()` function uses to confirm that integrated authentication should remain enabled. Without this relationship, the function defaults to `false` on every run. ↳ Script inlcude # sn_sccm_integrate.SCCMMultiDataSourceUtil # https://<instancename>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=174a7a0153f0301095e2ddeeff7b12aethis code 5. Save the record. 6. Confirm that the JDBC connection record associated with the custom alias has a valid credential record populated in the **Credential** field. Navigate to the `jdbc_connection` table and filter by the connection alias to verify. 7. Confirm that the Run As user on the scheduled import has one of the following roles: 'sn_cmdb_int_util.sgc_admin', 'import_scheduler', 'import_admin', or 'admin'. 8. Run the scheduled import and verify that the **Use Integrated Authentication** flag remains checked and the import completes without a login error. 9. If the login failure persists after completing the steps above, the issue may be external to the ServiceNow platform. Work with your SCCM database administrator to confirm that the MID Server host can access the target database on the target port and that the Windows service account running the MID Server has sufficient database permissions. 10. Enable the `glide.import.debug` system property to capture detailed import logs, then reproduce the failure and review the logs for additional context. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } - Configure the Service Graph Connector for SCCM - Troubleshooting JDBC connectivity and login to Microsoft SQL Server issues, including SCCM databases from the MID Server- SCCM initial setup — login failed for user