# Authorization

## Authorization Types

* [No auth](/working-with-project/authorization.md#no-auth) 
* [Inherit from parent](/working-with-project/authorization.md#inherit-from-parent) 
* [Basic auth ](/working-with-project/authorization.md#basic-auth)
* [Bearer auth](/working-with-project/authorization.md#bearer-auth) 
* [Digest Auth](/working-with-project/authorization.md#digest-auth) 
* [OAuth 1.0](/working-with-project/authorization.md#oauth-1-0)

{% hint style="info" %}
You can use [environment variables](/variables/env.md) as the Username, Password, Token, and other authorization parameters.
{% endhint %}

## No auth 

Use the No Auth type if you don't need authorization while sending a request.

## Inherit from parent 

**By default** authorization parameters are inherited from the parent node. If the parameters are not specified, the [No auth](/working-with-project/authorization.md#no-auth) type is used.

## Basic auth

The type is used when login and password are required for sending a request.

#### Using Basic auth

Open the request and click on the Authorization tab and choose Digest auth. Set the Username and Password in the corresponding fields.

![Using Basic auth](/files/-LhFkbR2YI_AGpENjeVK)

## Bearer auth 

Bearer auth is a token based authorization. Any user with the bearer token can use it to get the access to the resources.

#### Using Bearer auth

Open the request and click on the Authorization tab and choose Bearer auth. Set the token in the token field.

![Using Bearer auth](/files/-LhFktGKTScYA6iltlB5)

## Digest Auth 

Using this method, you send a hashed login, password, the server url and nonce values, which provides a higher security level than basic authorization, where you send data with no encryption.

#### Using Digest Auth

Open the request and click on the Authorization tab and choose Digest auth. Set the Username and Password in the corresponding fields.

![Using environment variables in Digest Auth](/files/-LhFl7UguhAzny4ZIv--)

## OAuth 1.0

OAuth 1.0 allows you to access protected resources without exposing your login and password.

#### Using OAuth 1.0

Open the request and click on the Authorization tab and choose OAuth 1.0. Input required data in the fields.

#### The OAuth 1.0 parameters supported in TestMace

| Parameters       | Description                                          |
| ---------------- | ---------------------------------------------------- |
| Consumer Key     | The key                                              |
| Consumer Secret  | The consumer code                                    |
| Access Token     | The token                                            |
| Token Secret     | The token code                                       |
| Signature Method | The signature Method: PLAINTEXT, HMAC-SHA1, RSA-SHA1 |
| Version          | 1.0                                                  |
| Realm            | The server the request is sent to                    |

![Using OAuth 1.0](/files/-LhFlV94xsc8cmlGmUbe)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testmace.com/working-with-project/authorization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.