
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2018 01:29 PM
Hi everyone,
I am trying to connect to 3rd party system using Outbound REST API. I wanted to understand what am I doing wrong in the authentication.
Endpoint is the GET API I am trying to refer-
http://*********************/tfs/*************/_apis/wit/workitems/116536?api-version=3.2
I am selecting the Authentication as Basic with my 3rd party userName and password. Our 3rd party server is on premise and we use our network credentials to login to that system. The network credentials are the username and password I have fed here.
I am also sending Authorization header in the request as -
The GET and POST APIs are working fine in Fiddler.
Here's a screenshot of the Test-
Any suggestions would be helpful.
Thanks,
Priyanka
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2018 10:45 AM
For all those who are running into the same issue as me,
You can either perform authentication through the Basic Auth/ Outh2.0 methods available on the REST API form, or you can send an Authorization header in the request. Doing both will not help you.
For the solution of this problem, I set my Authorization header as-
Authorization : Basic <myTokenHere>
Note- Your Authorization header can be different from mine depending upon the 3rd party system's API. My 3rd party was TFS.
and I set the Authentication to 'No Authentication'
This basically allowed my API to authenticate through token instead of the username and password specified in Basic Auth Profile.
Happy coding,
Priyanka

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2018 10:42 AM
Hey Aman,
I did set the MID server for the call. Thank you for your reply.
I have figured out why this wasn't working in the first place. Will post my solution as a separate comment here.
Thanks,
Priyanka

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2018 04:39 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2018 10:41 AM
Hi Rahul,
Yes, I know what the error means. As I wrote in my above reply, I already ran my API on Fiddler (a REST API Client like Postman) before I started running it on SN and things didn't pan out well.
Anyways, I have figured out why and would be posting my solution as a separate comment.
Thank you,
Priyanka

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2018 10:45 AM
For all those who are running into the same issue as me,
You can either perform authentication through the Basic Auth/ Outh2.0 methods available on the REST API form, or you can send an Authorization header in the request. Doing both will not help you.
For the solution of this problem, I set my Authorization header as-
Authorization : Basic <myTokenHere>
Note- Your Authorization header can be different from mine depending upon the 3rd party system's API. My 3rd party was TFS.
and I set the Authentication to 'No Authentication'
This basically allowed my API to authenticate through token instead of the username and password specified in Basic Auth Profile.
Happy coding,
Priyanka