---
title: Oasis STIX/TAXII2
slug: authentication-guides/oasis-stixtaxii2
docTags: 
createdAt: 2026-03-11T00:15:10.634Z
---

# Introduction

This guide tells you how to authenticate the OASIS TAXII2 connector in Swimlane. The connector supports HTTP Basic Authentication and Client Certificate Authentication.

You will configure authentication details for your TAXII server, collect the required credentials, and configure the connector asset in Swimlane Turbine.

# Prerequisites

## TAXII Server Access Requirements

You must have access to a TAXII 2.0 or TAXII 2.1 server with permissions to:

- Access TAXII collections
- Retrieve and submit STIX objects
- Use API authentication (HTTP Basic or Client Certificate)

# Required Credentials

Depending on the authentication method used, collect the following information:

- TAXII Server Root URL
- Username and Password (for HTTP Basic Authentication)
- Client Side Certificate (base64 encoded)
- Client Side Key (base64 encoded)
- TAXII version indicator (TAXII 2.1 enabled or disabled)

# Authentication Methods Overview

The OASIS TAXII2 connector supports the following authentication methods:

- HTTP Basic Authentication
- Client Certificate Authentication

# TAXII Server Setup

Authentication configuration depends on the TAXII server implementation. Take the following general steps to prepare authentication access.

1. Log in to your TAXII server administration console.
2. Create or identify a user account with access to TAXII collections.
3. Enable HTTP Basic Authentication for the account if required.
4. If certificate authentication is used, generate a client certificate and key.
5. Export the client certificate and key as base64 encoded strings.
6. Confirm whether your server supports TAXII 2.0 or TAXII 2.1.
7. Copy the TAXII server root URL.

# Connector Configuration in Swimlane

Take the following steps to configure the OASIS TAXII2 connector asset in Swimlane.

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

## Configuration – HTTP Basic Authentication

| **Field**          | **Description**                                | **Required** |
| ------------------ | ---------------------------------------------- | ------------ |
| url                | Root URL for TAXII2 server                     | Required     |
| username           | TAXII server username                          | Required     |
| password           | TAXII server password                          | Required     |
| client\_side\_cert | Base64 encoded client certificate (optional)   | Optional     |
| client\_side\_key  | Base64 encoded client key (optional)           | Optional     |
| taxii\_21          | True if connecting to a TAXII 2.1 server       | Required     |
| verify\_ssl        | Enable or disable SSL certificate verification | Optional     |
| http\_proxy        | Proxy configuration                            | Optional     |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/0SHl37j-PMM9lSBT-oSdp_image.png)

## Configuration – Client Certificate Authentication

| **Field**          | **Description**                                | **Required** |
| ------------------ | ---------------------------------------------- | ------------ |
| url                | Root URL for TAXII2 server                     | Required     |
| client\_side\_cert | Base64 encoded client certificate              | Required     |
| client\_side\_key  | Base64 encoded client key                      | Required     |
| taxii\_21          | True if connecting to a TAXII 2.1 server       | Required     |
| verify\_ssl        | Enable or disable SSL certificate verification | Optional     |
| http\_proxy        | Proxy configuration                            | Optional     |

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

# Troubleshooting

If authentication fails:

- Ensure the TAXII server URL is correct.
- Confirm the username and password are valid.
- Verify the client certificate and key are correctly base64 encoded.
- Ensure the TAXII version setting matches the server version.
- Check SSL verification and proxy settings if applicable.

**Sources**

- OASIS TAXII 2.0 Documentation: [https://docs.oasis-open.org/cti/taxii/v2.0/](https://docs.oasis-open.org/cti/taxii/v2.0/)
- OASIS TAXII 2.1 Documentation:[ https://docs.oasis-open.org/cti/taxii/v2.1/](https://docs.oasis-open.org/cti/taxii/v2.1/)

**Result**

You have successfully authenticated the OASIS TAXII2 connector in Swimlane.