Register your instance

task australia Updated Oct 27, 2026 2 min read register-your-instance.md
Raw file servicenow.com

Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.

Before you begin

Before registering, gather the following for each instance:

  • The exact instance name matching the instance_name system property (typically the subdomain — for example, companyname from companyname.service-now.com).
  • The full instance URL in the format https://instancename.service-now.com. Omit www., trailing slashes, and any path after the domain.
  • The environment type: Development, Production, or Test. Only one instance in your stack may be designated Production.

Role required: Scan Engine Admin (sn_se.scan_engine_admin)

Procedure

  1. Navigate to All > Impact > Configuration > Scan Engine Properties and open the My SN Instances related list tab.

  2. Select New for each instance and populate the following fields.

Field

Value

Instance Name

Must match the instance_name system property. To find the value, open stats.do in the instance and check the instance name.

Instance URL

https://instancename.service-now.com Select the lock icon next to the field to enter the URL.

Environment

Development, Production, or Test. This value determines which Scan Engine options appear on the instance. Only Development instances show the manual definition sync actions, and only one instance in the stack can be Production.

Authentication Type

API Credential Config

Appears when Authentication Type is Basic. Select the Basic authentication record for this instance.

OAuth Application Registry

Appears when Authentication Type is OAuth. Select the OAuth provider registry record.

OAuth User Profile

Appears when Authentication Type is OAuth. Select the OAuth user profile for the integration account.

3. Promote or export the My SN Instances list to all instances that will use Scan Engine integrations.
  1. On each target instance, open the imported production record and select Validate Connection.

    Connection Status updates to Connection Valid on success.

What to do next

If validation fails, resolve the root cause before retrying. Repeated failed attempts can trigger the account lockout policy. Refer to Validate your instance connection for additional information.

  • Configure the OAuth authentication method development instance
    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.
  • Configure the Basic authentication method
    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.
  • Validate your instance connection
    Validate the connection between registered instances to confirm that authentication and My SN Instances configuration are correct before enabling integrations.
  • Recover from account lockout
    Unlock the integration user account and clear the password reset flag after repeated failed validation attempts trigger the account lockout policy.

Parent Topic:Scan Engine integrations

Search documentation
Search document titles and file paths on the australia branch