![]() In any case, capturing HTTPS traffic seems like way overkill for the simple raw headers and payload I’m trying to view. I read documentation and got lost down rabbit holes because the cert files that are supposed to exist in %APPDATA%\Postman\proxy do not exist. I even tried the Capture requests functionality (Capture HTTPS traffic with Postman’s built-in proxy) but I can’t get it to work - seems to do nothing. This seems like a basic thing that lots of people would want, so I apparently just don’t know how to find that. But I have no way to compare because I can find no way to get Postman to reveal to me the raw request headers and raw body for the oauth authentication token request. NET client, either my headers are not matching postman’s headers (in the pre-call for getting the bearer token), or my POST body payload params are not matching postman’s. ![]() Important: Postman works fine, both for obtaining the bearer token AND for making the actual API call. Select View in Console to inspect the request details in the Console and find. When I run various experimental permutations, I get a different Bearer token from what postman gives me, and then when I use that bearer token in the actual API call against an endpoint, I get 401 unauthorized errors. Authenticate with Windows NTLM authentication in Postman. The actual problem: I’m having all kinds of trouble getting this postman request to work in my c# app. (even something similar to the “code” icon’s code generation).If actual params, what is their actual name in the payload? It would be so very nice if after executing this request (by clicking Get New Access Token), I could click a button and see the low-level items such as: And I don’t know if they go into the headers and whether they need to be url-encoded. I don’t know if these are actual params or optional things. But then we get to other params like Token Name, Callback URL, and Access Token URL. I happen to know that under the hood that is actually a POST param named client_id.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |