Outbound Web Service Basic Authentication issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2013 10:10 AM
Hello everyone,
I am testing an outbound Web Service call to a 3rd party application. The web service works fine in SoapUI using "Global HTTP Settings" and WSS-PAssword Type of "PasswordText", but fails with "invalid username or password" using Basic Authentication set in ServiceNow.
I am able to get the Web Service to work from ServiceNow by adding the un-encrypted login and password using the following structure, but I wanted to know if there was a more secure way to get it working from ServiceNow. Could the problem be special characters in the username or password? Any suggestions on how to get it working with Basic Authentication? Do I need a Java KeyStore? Thanks!
MyUsername@domain
MyPassword
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2013 10:02 AM
Did you get an answer to this? I'm in the same boat or at least somewhat close. I need to specify a domain to be able to authenticate to my web service.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2013 10:33 PM
So the issue is that your really using WEb Service Security, not basic Auth.
Actually both ways are equally secure with how the soap envelope is sent. It really depends on whether or not your endpoint is using SSL. Because basic Auth credentials are just base64 encoded in a header, while your XML contains the credentials non encoded. But either one is completely insecure if passed over an http connection. And both are quite secure if passed over https.
Long story short, passing the credentials in the wsse header is just as secure and the correct way to perform wsse from SnC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2013 11:14 PM
After doing a bit more research it looks like its ntlm authentication. We're trying to connect to a sharepoint lists web service and haven't had any luck. It appears I need some way to specify a domain..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2013 05:58 AM
Yes, but in my specific case, using the build in "username" and "password" fields that include the credentials in the header were not working. The format that the endpoint was expecting did not match the format SnC was sending. Is there a documented way to modify the headers?
-Ken
