Integrations across multiple instances

concept australia Updated Oct 28, 2026 2 min read multi-instance-integration.md
Raw file servicenow.com

A stack with more than two instances needs an OAuth provider registry and an OAuth client registry for every instance in the stack.

A development and production pair is the simplest integration stack. Most organizations run more non-production instances, such as development, QA, and test. In that case, every instance in the stack needs an OAuth provider registry and an OAuth client registry for each instance, and you export those records to every instance.

Stack model

Instance role Records required
Production A My SN Instances record for itself, marked Production, and one for each non-production instance it communicates with.
Each non-production instance A My SN Instances record for itself, marked Development or Test, and one for production.
Every instance in the stack An integration user, and an OAuth provider registry and an OAuth client registry for each instance in the stack. Export both records to every instance. In a stack of development, test, and production, each instance has six OAuth registry records, one provider and one client for each instance.

Important: Only one instance in the stack can be designated Production.

Setup order

Complete the setup for the first development and production pair before you add more instances. Then repeat the non-production steps for each additional instance.

  1. Create the integration user on each instance, using Create an integration user account.
  2. Register every instance in the stack, using Register your instance.
  3. Set up OAuth for the first development and production pair, using Configure the OAuth authentication method development instance and Configure the OAuth authentication method production instance.
  4. For each additional non-production instance, create an OAuth provider registry and an OAuth client registry on that instance. Export both records, and import them into every other instance in the stack. Then create the My SN Instances record for that instance on production.
  5. Grant KMF access on each instance that receives imported records, using Grant Key Management Framework access on an instance.
  6. Validate every My SN Instances record on every instance, using Validate your instance connection.

Parent Topic:Scan Engine integrations

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