<commit_before>---
categories:
  - "postman"
  - "sending_api_requests"
title: "Authorization"
page_id: "authorization"
warning: false

---
**(Significant changes to the Authorization flow. Propose to retire this topic and replace with new topic.)**

While the request editor is powerful enough to construct any kind of requests, sometimes you might need some help. Postman has “helpers”, which can simplify some repetitive and complex tasks. The current set of helpers let you deal with authentication protocols easily. You can use environment variables with all helpers.

You can choose to save helper data to collection requests. This will cause the signature to be regenerated each time. These helpers will even work in Newman!


> [![preview request button](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/authButton.png)](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/authButton.png)
  **Update**: Starting with Postman 5.3, you will notice a few changes around the request authorization flows. Postman has updated the authorization framework to improve existing authorization types, like OAuth 2.0, and also introduced new authorization types, like NTLM. Additionally, there is no need to manually update the request. If you want to inspect the authorization headers and parameters that Postman generates, you can use the **Preview Request** button. Alternatively, inspect the [Postman console](/docs/postman/sending_api_requests/debugging_and_logs) to get a raw dump of the entire request after it is sent. 

### Basic Auth

[![basic auth](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/58961418.png)](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/58961418.png)

Enter the username and password fields and hit “Update Request” to generate the authorization header.

### Digest Auth
<commit_msg>Update 2017-05-04-authorization.md<commit_after>---
categories:
  - "postman"
  - "sending_api_requests"
title: "Authorization"
page_id: "authorization"
warning: false

---
The authorization process verifies whether a user has permission to access the data you want from the server. When you send a request, you often have to include parameters to ensure the request has permission to access and return the data you want. 
Postman provides authorization types that make it easy for you to handle authentication protocols in Postman native apps.

When you select Authorization in the request builder, you see the TYPE drop down menu. 
* No Auth 
* Bearer Token
* Basic auth
* Digest Auth
* OAuth 1.0
* OAuth 2.0
* Hawk Authentication
* AWS Signature
* NTLM Authentication [Beta]

**Note**: availability of features in native apps

> [![auth menu](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/auth_menu.png)](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/auth_menu.png)




### No Auth

By default ‘No Auth’ appears first on the drop down menu list. Use ‘No Auth’ when you don’t need an authorization parameter to send a request. 
  
### Basic Auth

[![basic auth](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/58961418.png)](https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/58961418.png)

Enter the username and password fields and hit “Update Request” to generate the authorization header.

### Digest Auth

{'fraction_non_alphanumeric': 0.08698224852071006, 'fraction_numerical': 0.016568047337278107, 'mean_word_length': 4.789383561643835, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '259099', 'n_tokens_mistral': 971, 'n_tokens_neox': 925, 'n_words': 377}