Hello fellow RPT users/developers:
I'm working on a project in which we're testing an integration between MS-Outlook 2010 and a web based J2EE application. I've successfully captured HTTP traffic from a plugin in Outlook to our web based application, however, an essential request header that was recorded in the script is not being sent during replay. The specific request header is an "Authorization" header that is required for basic authentication.
Has anyone dealt with such an issue or do you have any suggested workarounds/fixes? I've attached some screen shots of the header and test log comparisons for more context. Thank you for your time in reading my post!
Pinned topic RPT v220.127.116.11 - Issue w/Request Headers
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-10T08:51:58Z at 2012-11-10T08:51:58Z by SystemAdmin
Re: RPT v18.104.22.168 - Issue w/Request Headers (or Basic Authentication?)2012-09-12T20:42:02ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
As mentioned in the original post, Authorization Headers were captured during recording yet were not sent during replay. During debugging, two iterations of the same business process were re-recorded. In the first iteration, Basic Auth. credentials (along with Authorization Headers) were recorded. However, in the second iteration only Authorization Headers were recorded.
It was observed that Basic Authentication always failed during replay of the test script. However, when Basic Auth. in the first iteration was commented out OR when the second iteration (without Basic Auth.) was replayed, the subsequent requests were successful.
I attempted to put the Basic Auth. credentials in a Datapool, but it resulted in the same request failure. If you've had any experience or troubleshooting Basic Auth. issues in RPT, your feedback is appreciated. Thanks!