---
title: ServiceNow
slug: authentication-guides/servicenow
docTags: 
createdAt: 2026-01-19T20:45:53.831Z
---

# 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: 

1. Log in to your ServiceNow instance.
2. Navigate to **System OAuth > Application Registry**.
3. Create an **OAuth API **endpoint for external clients if required.
4. Copy the **Client ID **and **Client Secret**.
5. Determine your** ServiceNow REST API** base URL.

# Connector Configuration in Swimlane

1. Log in to Turbine.
2. From the left-hand navigation pane, click **ORCHESTRATION** and click **Assets**.
   Asset homepage opens.
3. Click the **plus** icon to open the Configure your Connector Asset window.
4. Select ServiceNow from the Asset type list.
5. Fill in the **Asset Settings **and **Asset Input** as shown as per your authentication method:

## Configuration - HTTP Basic Authentication

| **Field**   | **Description**                    | **Required/Optional** |
| ----------- | ---------------------------------- | --------------------- |
| url         | A URL to the target host.          | Required              |
| username    | Username                           | Required              |
| password    | Password                           | Required              |
| verify\_ssl | Verify SSL certificate             | Optional              |
| http\_proxy | A proxy to route requests through. | Optional              |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/MCn9QQJ8LVLCPQN_GCuZ3-20260121-062857.png)

## Configuration - OAuth 2.0 Client Credentials

| **Field**      | **Description**                    | **Required** |
| -------------- | ---------------------------------- | ------------ |
| url            | A URL to the target host.          | Required     |
| token\_url     | Token URL.                         | Required     |
| client\_id     | Client ID                          | Required     |
| client\_secret | Client Secret                      | Required     |
| scope          | Permission scopes                  | Optional     |
| verify\_ssl    | Verify SSL certificate             | Optional     |
| http\_proxy    | A proxy to route requests through. | Optional     |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/QKtmaNZVYxHZhpdaZXAJu-20260121-062858.png)

## Configuration – OAuth 2.0 Password Grant

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/0vlYoHDl52BianGd0CBni-20260121-062858.png)

| **Field**        | **Description**                    | **Required/Optional** |
| ---------------- | ---------------------------------- | --------------------- |
| url              | A URL to the target host.          | Required              |
| client\_id       | Client ID                          | Required              |
| client\_secret   | Client Secret                      | Required              |
| scope            | Permission scopes                  | Optional              |
| oauth2\_username | Username                           | Required              |
| oauth2\_password | Password                           | Required              |
| verify\_ssl      | Verify SSL certificate             | Optional              |
| http\_proxy      | A proxy to route requests through. | Optional              |

6. 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.
  &#x20;Example formats: https\://\<instance>.service-now\.com/api/...
- **Invalid OAuth credentials**
  &#x20;Verify that the **Client ID** and **Client Secret** match the values generated in **ServiceNow → System OAuth → Application Registry**.
- **Insufficient permissions**
  &#x20;Confirm that the authenticated user or OAuth application has the required roles and access to use the **ServiceNow REST API**.
- **SSL verification errors**
  &#x20;If SSL inspection or certificate rewriting is used in your environment, set verify\_ssl to false or update certificates accordingly.
- **Proxy configuration issues**
  &#x20;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.

****