---
title: Google Chronicle Search
slug: authentication-guides/google-chronicle-search
docTags: 
createdAt: 2026-06-22T10:01:22.947Z
---

# Introduction

This guide tells you how to authenticate the **Google Chronicle Search connector** in Swimlane using **OAuth 2.0 Service Account Authentication**.

You will create a Google Cloud service account, assign the required permissions, generate a JSON key file, collect the required identifiers, and configure the connector in Swimlane.

# Prerequisites

### Google Chronicle Access Requirements

You must have Google Cloud permissions to:

- Access the Google Chronicle platform
- Create and manage Service Accounts
- Generate Service Account JSON keys
- Assign Chronicle API permissions
- Access Google Security Operations APIs

### Required Credentials

During setup, you will collect:

- Google Chronicle API Base URL
- Service Account JSON Key File
- OAuth Scopes

## Authentication Methods Overview

The Google Chronicle Search connector supports:

- **OAuth 2.0 Service Account Authentication**

# Google Chronicle Setup

Take the following steps to create a Service Account:

1. Log in to the **Google Cloud Console**.
2. Navigate to **IAM & Admin → Service Accounts**.
3. Click **Create Service Account**.
4. Enter:
   - Service Account Name
   - Description
5. Click **Create and Continue**.
6. Assign appropriate Chronicle or Security Operations roles.
7. Click **Done**.

Take the following steps to generate a JSON Key File:

1. Open the created **Service Account**.
2. Navigate to the **Keys** tab.
3. Click **Add Key → Create New Key**.
4. Select **JSON**.
5. Click **Create**.
6. Download and securely store the JSON key file.

Take the following steps to Base64 encode the JSON Key File:

The Swimlane connector requires the Service Account JSON contents to be Base64 encoded.

**Linux / macOS**

`base64 service-account.json`

**Windows PowerShell**

`[Convert]::ToBase64String([IO.File]::ReadAllBytes("service-account.json"))`

Copy the generated Base64 string for use in Swimlane.

### Regional Endpoints

| **Region**                 | **Endpoint**                                                                                                     |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| United States Multi-Region | [https://backstory.googleapis.com/](https://backstory.googleapis.com/)                                           |
| European Multi-Region      | [https://europe-backstory.googleapis.com/](https://europe-backstory.googleapis.com/)                             |
| London                     | [https://europe-west2-backstory.googleapis.com/](https://europe-west2-backstory.googleapis.com/)                 |
| Singapore                  | [https://asia-southeast1-backstory.googleapis.com/](https://asia-southeast1-backstory.googleapis.com/)           |
| Sydney                     | [https://australia-southeast1-backstory.googleapis.com/](https://australia-southeast1-backstory.googleapis.com/) |
| Tel Aviv                   | [https://me-west1-backstory.googleapis.com/](https://me-west1-backstory.googleapis.com/)                         |

# Connector configuration in Swimlane

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

**Configuration – OAuth 2.0 Service Account Authentication**

| **Field**          | **Description**                              | **Required** |
| ------------------ | -------------------------------------------- | ------------ |
| b64\_service\_info | Base64-encoded Service Account JSON contents | Yes          |
| url                | Google Chronicle regional API endpoint       | Yes          |
| scopes             | OAuth scopes required for Chronicle APIs     | Yes          |
| verify\_ssl        | Enable or disable SSL verification           | No           |
| http\_proxy        | Proxy configuration                          | No           |

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

# Recommended OAuth Scopes

| **Scope**                                                                                                  | **Purpose**              |
| ---------------------------------------------------------------------------------------------------------- | ------------------------ |
| [https://www.googleapis.com/auth/cloud-platform](https://www.googleapis.com/auth/cloud-platform)           | Access Google Cloud APIs |
| [https://www.googleapis.com/auth/chronicle-backstory](https://www.googleapis.com/auth/chronicle-backstory) | Access Chronicle APIs    |

# Troubleshooting

Authentication failures may occur due to:

- Incorrect Base64 encoding
- Invalid Service Account JSON file
- Missing Chronicle API permissions
- Incorrect regional endpoint
- Invalid OAuth scopes

### Fix:

- Ensure the JSON file is correctly Base64 encoded
- Verify Service Account permissions
- Confirm the correct Chronicle regional endpoint
- Verify assigned OAuth scopes
- Regenerate Service Account keys if necessary

You have successfully authenticated the **Google Chronicle Search connector** in Swimlane.

### Sources

- Google Chronicle API Documentation:
  [https://cloud.google.com/chronicle/docs/reference](https://cloud.google.com/chronicle/docs/reference)
- Google Chronicle Search API Documentation:
  [https://cloud.google.com/chronicle/docs/reference/search-api](https://cloud.google.com/chronicle/docs/reference/search-api)
- Google Cloud Service Accounts Documentation:
  [https://cloud.google.com/iam/docs/service-accounts](https://cloud.google.com/iam/docs/service-accounts)
- Google Cloud Service Account Keys Documentation:
  [https://cloud.google.com/iam/docs/keys-create-delete](https://cloud.google.com/iam/docs/keys-create-delete)