CODEWITHSUNDEEP
c#httppostmanhttp-getdynamics-crm-2016
Alex Gordon
Alex Gordon

Reputation: 60731

GET request works in browser, but I get Unauthorized when using Postman

I am issuing a request via chrome: 

[org]/api/data/v8.1/accounts?$select=name,accountid&$top=3

and I get a reasonable response:

{
  "@odata.context":"[org]/api/data/v8.1/$metadata#accounts(name,accountid)","value":[
    {
      "@odata.etag":"W/\"769209\"","name":"Telco","accountid":"c6ed63e0-9664-e411-940d-00155d104b35"
    },{
      "@odata.etag":"W/\"752021\"","name":"Fourth Coffee","accountid":"d1eefc0a-3ebc-e611-80be-24be051ac8a1"
    },{
      "@odata.etag":"W/\"768036\"","name":"Fourth Coffee","accountid":"3cbb8d24-20bd-e611-80c0-24be051ac8a1"
    }
  ]
}

However, when attempting to do the same GET through postman, I am getting a 401 unauthorized!

I've tried with no headers at all, as well as basic auth:

Authorization:Basic Y2hybGFiXxxxxxxxxxxxxxcmQxMjM=

What am I doing wrong? Is there something I need to change within CRM to allow me to do GETs from postman?

The following are headers that Chrome uses (got this from DevTools):

Upvotes: 9

Views: 58525

Answers (9)

gouravm
gouravm

Reputation: 321

In my case in .NET project i had two different authentication schemes in my Startup.cs . I removed the older one and added its auth services and it worked.

Upvotes: 1

juubaker
juubaker

Reputation: 1

If request works from the browser, then no authentication was used.
So, in Postman, for Authentication, use No Auth. :-)

Upvotes: -2

CodeSlave
CodeSlave

Reputation: 495

I used the following steps and it was ok. Follow the steps, below:

  1. Open Google Chrome
  2. Install Postman Extention
  3. Install Postman's Interceptor Extention
  4. Open Postman Extention
  5. Use Sync
  6. Use Interceptor

Upvotes: 1

Rajeshwar
Rajeshwar

Reputation: 975

This solved my issue. In Postman, I copied the Access Token from Authorization tab and I have selected "No Auth" Type. Then, I moved to Headers tab, Under Headers section, I have provided new Key with Name "Authorization" and in the Value I have passed my TOKEN prefix with Bearer.See the below screenshot

Upvotes: 0

Priyanka Arora
Priyanka Arora

Reputation: 457

These helped me.

  1. Check that it is NTLM authentication both in postman and in the page hosted it is checked.

  2. Use method post

  3. Username and password(which you have set and need not be the access key)

Upvotes: 0

sami
sami

Reputation: 733

Try putting quotes around your url:

curl '[org]/api/data/v8.1/accounts?$select=name,accountid&$top=3'

The &, $, = etc. may be causing problems - I had the same problem and putting quotes was the resolution

Upvotes: 0

kothari
kothari

Reputation: 92

You are trying to access from the postman chrome extension or through the postman( windows based) installed application on your system.Try to fetch the data from chrome extension.

Upvotes: 1

Alex
Alex

Reputation: 23300

First, login into CRM and leave the tab sitting there.

Go into POSTMan

Enable the Interceptor (see image) interceptor

Enter the URL and hit SEND, just like that. POSTMan will take care of cookies and headers on its own, and you'll see the results.

If you logout from CRM, POSTMan will obviously no longer be able to issue the requests and will return 401 instead.

Upvotes: 6

xpa1492
xpa1492

Reputation: 1973

It seems like the server you are calling requires RFC 4559 (https://www.rfc-editor.org/rfc/rfc4559) authentication. More details here: https://en.wikipedia.org/wiki/SPNEGO.

The way it works in the case of a GET request from the browser:

  1. Browser requests the required page
  2. The server responds with HTTP 401 (Unauthorized) and provides a response header WWW-Authenticate: Negotiate. This tell the browser that RFC 4559 authentication is required.
  3. The browser makes sure the site has permissions for this action (details on configuration here: https://ping.force.com/Support/PingFederate/Integrations/How-to-configure-supported-browsers-for-Kerberos-NTLM). Most sites will not be allowed to request such authorization without being explicitly white-listed.
  4. If permitted, the browser requests a Kerboros ticket from the domain's Active Directory.
  5. Active Directory responds with a ticket.
  6. The browser forward the ticker to the server (via the Authotizarion: Negotiate xxxxx header that you see).
  7. The server interacts with the same Active Directory and turns that ticket into username and groups/permissions information.

I am not aware of a tool that will let you do this (simulate a browser) if you are trying to automate requests against the server (which is probably an internal/intranet company site). Your best course of action may be some form of scripting (like VBS) which will use IE via COM and possibly handle this authentication for you (I have not done this, so not sure if it will indeed work).

Upvotes: 4

Related Questions