ServiceNow

introduction this guide explains how to authenticate the servicenow connector in swimlane the connector supports three authentication methods oauth 2 0 client credentials oauth 2 0 password grant http basic authentication you will collect the required credentials, configure authentication parameters, and set up the connector inside swimlane prerequisites servicenow access requirements access the servicenow rest api retrieve account credentials or api oauth credentials have roles permitting api usage required credentials for oauth 2 0 client credentials url client id client secret token url scope for oauth 2 0 password grant url client id client secret username password token url for http basic authentication url username password authentication methods overview oauth 2 0 client credentials used for server to server authentication you will need client id client secret token url scope(s) oauth 2 0 password grant used for delegated user authentication you will need client id client secret username password token url scope(s) http basic authentication simple username/password authentication you will need url username password servicenow setup take the following steps to prepare servicenow credentials log in to your servicenow instance navigate to system oauth > application registry create an oauth api endpoint for external clients if required copy the client id and client secret determine your servicenow rest api base url connector configuration in swimlane log in to turbine from the left hand navigation pane, click orchestration and click assets asset homepage opens click the plus icon to open the configure your connector asset window select servicenow from the asset type list fill in the asset settings and asset input as shown as per your authentication method configuration http basic authentication true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type configuration oauth 2 0 client credentials true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type configuration – oauth 2 0 password grant true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type click create troubleshooting if you encounter authentication issues with the servicenow connector, review the following common causes and resolutions incorrect url ensure the servicenow rest api base url is correct for your instance example formats https //\<instance> service now\ com/api/ invalid oauth credentials verify that the client id and client secret match the values generated in servicenow → system oauth → application registry insufficient permissions confirm that the authenticated user or oauth application has the required roles and access to use the servicenow rest api ssl verification errors if ssl inspection or certificate rewriting is used in your environment, set verify ssl to false or update certificates accordingly proxy configuration issues if your environment uses a proxy, ensure the http proxy value is correctly formatted and that the proxy allows outbound connections to servicenow you have successfully authenticated the servicenow connector using one of the supported authentication methods