Bug 62716

Summary:	When Recording, JMeter removes Authorization from generated Header Manager when using Bearer Token
Product:	JMeter - Now in Github	Reporter:	UbikLoadPack support <support>
Component:	HTTP	Assignee:	JMeter issues mailing list <issues>
Status:	RESOLVED FIXED
Severity:	normal	CC:	p.mouawad
Priority:	P2	Keywords:	FixedInTrunk
Version:	3.0
Target Milestone:	JMETER_5.0
Hardware:	All
OS:	All

Description UbikLoadPack support 2018-09-13 15:10:38 UTC

When an application uses Authorization header but Bearer token, JMeter wrongly deduces that it is Kerberos and removes the Authorization from HeaderManager.

This is problematic for 2 reasons:

- The auth policy is wrong
- The Authorization is removed while it should be correlated by user or Managed correctly by JMeter

Comment 1 Philippe Mouawad 2018-09-13 20:23:13 UTC

pmouawad@apache.org
	
10:20 PM (2 minutes ago)
	
to commits
Author: pmouawad
Date: Thu Sep 13 20:20:15 2018
New Revision: 1840863

URL: http://svn.apache.org/viewvc?rev=1840863&view=rev
Log:
Bug 62716: When Recording, JMeter removes Authorization from generated Header Manager when using Bearer Token
Bugzilla Id: 62716

Modified:
    jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/proxy/ProxyControl.java
    jmeter/trunk/xdocs/changes.xml

Comment 2 The ASF infrastructure team 2022-09-24 20:38:14 UTC

This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4862