---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Validate your instance connection

# Validate your instance connection {#ariaid-title1}

* Release version: Australia
* 
* Updated May 5, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Validate the connection between registered instances to confirm that authentication
and My SN Instances configuration are correct before enabling integrations.

## Before you begin

My SN Instances registration and authentication must be complete before validating. See [Register your instance](https://servicenow-prod.fluidtopics.net/CW_9LTbn1YISzXh4d4sYSg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.") and either [Configure the Basic authentication method](https://servicenow-prod.fluidtopics.net/cuVzGTUp4EYPFdAvW75jrw "Confirm an integration user, create a Basic authentication record, then connect your instances using basic authentication. Basic authentication is supported but OAuth is recommended for production environments.") or [Configure the OAuth authentication method development instance](https://servicenow-prod.fluidtopics.net/1yaYVDnxfcmFLl6Jpf0k0A "Set up OAuth authentication for instance-to-instance Scan Engine integrations using several stages, an integration user account, an OAuth2 configuration record, and provider and client application registries.").

Role required: `sn_se.scan_engine_admin`

## Procedure

1. Navigate to ALLImpactConfigurationScan Engine PropertiesMy SN Instances.
2. Open the instance record to validate.
3. Select Validate Connection.  
   Connection Status updates to Connection valid.

## What to do next

If validation fails, resolve the root cause before retrying. Retrying without fixing the
root cause can trigger the account lockout policy. Work through the following checks in
order:

1. The integration user password was set using `setDisplayValue()` on this instance.
2. The authentication record password was re-entered in the UI on this instance.
3. Both roles --- `sn_se.scan_engine_admin` and `sn_se.internal_rest_integration` --- are explicitly assigned to the integration user on this instance.
4. The instance URL is exactly `https://instancename.service-now.com` with no `www.`, trailing slash, or path.
5. Any pending Scan Engine scripting scope request in Key Management Framework access policies has been approved, and you have logged out and back in before retrying.
   1. Assign the system administrator role the Key Management admin role
   2. Assign the sn_kmf.cryptographic_manager role to the system admin.
   3. Navigate to AllKey ManagementModule Access Policies.
   4. Search for Scan Engine in the Script Table Target script: Script Include: ScanEngineApiUtil
   5. Open the record and set the Result to Track.

If the account has been locked out, see [Recover from account lockout](https://servicenow-prod.fluidtopics.net/lMPugVEbEymyhoAQqCLFOg "Unlock the integration user account and clear the password reset flag after repeated failed validation attempts trigger the account lockout policy.").

*[\>]: and then