pv7721
10 years agoOccasional Contributor
REST application authentication in headers - not working
Hello,
I have to test a REST application for which the authentication scheme is to pass along a couple of specific headers (Password and Username) with each request.
For the most basic request, getting the system's date, I've added those 2 headers to be passed along (and I've noticed that they're automatically reordered alphabetically, thus Password is sent first.
The URL scheme is HTTP which gets redirected to HTTPS (self-signed certificate). I keep getting HTTP/1.1 401 Authorization Required while using SoapUI, whereas with a REST client in browser I get my result (and even the order of parameters doesn't seem to matter).
Can anybody point me to the right direction or tell me what I might be doing wrong?
Thanks!
I have to test a REST application for which the authentication scheme is to pass along a couple of specific headers (Password and Username) with each request.
For the most basic request, getting the system's date, I've added those 2 headers to be passed along (and I've noticed that they're automatically reordered alphabetically, thus Password is sent first.
The URL scheme is HTTP which gets redirected to HTTPS (self-signed certificate). I keep getting HTTP/1.1 401 Authorization Required while using SoapUI, whereas with a REST client in browser I get my result (and even the order of parameters doesn't seem to matter).
Can anybody point me to the right direction or tell me what I might be doing wrong?
Thanks!