[#MIRTH-2282] Add preemptive authentication as an option in the

advertisement
[MIRTH-2282] Add preemptive authentication as an option in the HTTP
Sender Created: 29/Nov/12 Updated: 18/Sep/14 Resolved: 23/Jun/14
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
Mirth Connect
Administrator, Server
None
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
New Feature
Major
Priority:
Nick Rupley
Nick Rupley
Assignee:
Fixed
0
Votes:
Apache, HTTP, HttpClient, Jakarta, Sender, authentication, preemptive
Not Specified
Issue Links:
Relates
relates to MIRTH-3357 Add option for preemptive authenticat... Open
is related to MIRTH-3273 Preemptive authentication does not wo... Closed
Assigned QA:
Eduardo Armendariz
3.1.0
Not Specified
Not Specified
Description
Currently when authentication is enabled in the HTTP Sender, the credentials are always sent
preemptively in the initial request. Although the current version of HttpClient supports settings
this option, that was removed from the latest version due to security concerns (see here:
http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html). It's obviously
still possible to perform preemptive authentication with version 4.1 though, just not out of the
box.
Instead of always authenticating with the first request, the HTTP Sender should have an option
in the UI to let the user decide. The Yes/No radio buttons could be changed to
"Always/Never/On Request" for example.
Comments
Comment by Nick Rupley [ 23/Jun/14 ]
Revision 7202: Added an option for preemptive authentication to the HTTP Sender.
Comment by Eduardo Armendariz [ 18/Sep/14 ]
Showed in that preemptive(and non preemptive) digest authentication is working.
(rev 7384)Verified that preemptive and non preemptive basic authentication are working. Only
preemptive will now send the Authorization header before a challenge. If the channel depends
on a challenge then it the realm is required, if the server does not include a realm then auth will
fail.
Generated at Tue Feb 09 05:15:00 PST 2016 using JIRA 6.2.7#6265sha1:91604a8de81892a3e362e0afee505432f29579b0.
Download