---
title: "OAuth 1.0"
slug: "oauth-10"
updated: 2024-02-08T19:42:13Z
published: 2024-02-08T19:42:13Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# OAuth 1.0

OAuth 1.0 is a token-based authentication method supported for HTTP Connectors. It provides an application with an access token for request authentication.

This methos uses HMAC-SHA signature strings. These strings hash the algorithms used to generate the signature for the request.

## Components

- **User** -  person who wants to get access
- **Consumer** - application or website that uses OAuth to access the Service Provider (Tulip)
- **Service Provider** - web application that allows access via OAuth (Netsuite)
- **Protected Resource** - data the user wants to access

## Tokens

OAuth 1.0 uses a request token and access token.

- **Request Token** - a token containing Consumer Key and Consumer Secret used to ask the service for authorization
- **Access Token**  - a token used to access the resource

Additionally, long-lived tokens, typically valid for a year or more

![OAuth 1.0.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/OAuth%201.0.png)

**Connectors**

**Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions.

- **HTTP Connectors** utilize HTTP API endpoints.
- **SQL Connectors** can enable connectivity with certain SQL databases.
- **MQTT Connectors** can connect to MQTT brokers for machine monitoring.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif)