ServiceNow

the servicenow integration can be configured via resolve's ui or on the resolve satellite prerequisite you will need permissions to create integrations in servicenow as well as access to your organization's resolve ai integration page https //app0 resolve ai/integrations/servicenow/connect 1\ in servicenow, create the integration in servicenow ui, open inbound integrations click new integration pick oauth client credentials grant choose an application user role that has access these tables cmdb rel ci cmdb ci copy both client id and client secret to use in the next step if your servicenow instance restricts inbound traffic by ip (system security > ip address access control), add an allow rule for 3 16 200 209/32 so resolve ai's cloud can reach your instance this is only required when connecting from the resolve ai cloud — satellite based connections originate from your own infrastructure 2\ in resolve ai, connect the integration option a from the resolve app log in to resolve ai and open the servicenow integration page https //app0 resolve ai/integrations/servicenow/connect name the integration, ex production servicenow pick environments that resolve ai will connect to, for example production and staging client id paste in from servicenow client secret paste in from servicenow option b setup from the satellite create a kubernetes secret to hold your servicenow inbound integration’s client id and client secret apiversion v1 kind secret type opaque metadata name servicenow resolve access token stringdata clientid "\<your client id>" clientsecret "\<your client secret>" on the command line, apply the secret kubectl apply f servicenow resolve access token yml add the servicenow integration to your resolve satellite’s configuration by updating the resolve values yaml file integrations servicenow type servicenow create true secretname servicenow resolve access token connection url "https //yourcompany service now\ com" on the command line, update the satellite with the new resolve values yaml file helm upgrade install resolve satellite \\ oci //registry 1 docker io/resolveaihq/satellite chart \\ \ values resolve values yaml finally, check the status of the satellite on your organization's integration page https //app0 resolve ai/integrations https //app0 resolve ai/integrations troubleshooting older servicenow versions (yokohama and earlier) if you don't see oauth client credentials grant as an option when creating the integration, or the connection fails after setup, the following servicenow side settings may need to be configured these are typically pre configured on newer instances but have been seen to be missing on yokohama and earlier versions enable the client credentials grant type the client credentials inbound oauth flow is gated by a system property that may not be set by default in servicenow, navigate to system properties > all properties and click new fill in the form name glide oauth inbound client credential grant type enabled type true | false value true click save add the oauth application user field to the form the oauth application user field is hidden from the oauth application registry form by default and must be added before you can assign the application user that resolve ai will authenticate as open the application registry record for resolve ai from the context menu (≡), choose configure > form layout move oauth application user into the selected column and save back on the record, set oauth application user to the user whose role grants the required cmdb rel ci and cmdb ci table access for servicenow's reference documentation on this flow, see client credentials grant flow (yokohama) https //www servicenow\ com/docs/bundle/yokohama platform security/page/integrate/authentication/concept/client credentials html