JMeter - Config Element - "HTTP Authorization Manager"

HTTP Authorization Manager is used to handle browser authentication pop-up. Many times you have seen while downloading a file from an FTP server, a "gatekeeper" pop-up appears which is shown below. 

This pop-up window is generated by a browser when the server requires a username/password. The frame will vary from browser to browser (e.g. Mozilla Firefox, Apple Safari, or Microsoft Internet Explorer), but regardless, a username/password is required to access what are often some basic resources. That’s where the term "HTTP Authorization" comes from and you can handle this using “HTTP Authorization Manager”.

The Authorization Manager lets you specify one or more user logins for web pages that are restricted using server authentication.

Note: HTTP Authorization headers are not shown in the View Results Tree Listener so we won't be able to check their values from the test script.

How to add "HTTP Authorization Manager" element?
You can follow below steps:

1. Select "Test Plan" node

2. Right click on "Test Plan" node
3. Mouse hovers "Add"
4. Mouse hovers "Config Element"
5. Click "HTTP Authorization Manager"

How to remove "HTTP Authorization Manager" element?

You can follow below steps:

1. Select "HTTP Authorization Manager" node
2. Right click on "HTTP Authorization Manager" node
3. Click "Remove" (Mouse) or "Delete" button from the keyboard

4. Click "Yes"

What are the attributes of "HTTP Authorization Manager" element?
"HTTP Authorization Manager" has below attributes:

• Name: To provide element name
• Comments: To provide arbitrary comments (if any)
• Clear auth on each iteration?: This option is used by Kerberos authentication. If checked, authentication will be done on each iteration of main Thread Group loop even if it has already been done in a previous one. This is usually useful if each main thread group iteration represents the behaviour of one Virtual User.
• Base URL: A partial or complete URL that matches one or more HTTP Request URLs.
• Username: The username to provide for authorization. 
• Password: The password to provide for authorization. 
• Domain: The domain to use for NTLM.
• Realm: The Realm to use for NTLM. The Realm only applies to the HttpClient sampler.
• Mechanism: The Type of authentication to perform. JMeter can perform different types of authentications based on used Http Samplers:

1. Java

• BASIC

2. HttpClient 3.1

• BASIC
• DIGEST

3. HttpClient 4

• BASIC
• DIGEST
• KerberosChoose 

Next Topic:
Apache JMeter - "HTTP Cache Manager" Element

Previous Topic:
Apache JMeter - "FTP Request Defaults" Element

Related Topics:

• oAuth 2.0 Login Issue
• Config Elements
• Apache JMeter