I just installed the Windows app version of Postman. Previously I have been using the Chrome plugin. It seems the Windows version is not passing through my Windows credentials to my ASP.Net Web API application. I get 401.2 errors.
The same exact call works fine from the Chrome plugin.
Is there a configuration I am missing perhaps?
Thank you
Karl
Related
I would like to get the download path for web browser clients.
How do I detect the default download path on a client PC in an asp.net core 3.1 project (c#)?
Poul Bak's comment is correct.
As we know, .net core 3.1 webapp just support broswer to access the resource from the webserver. It can't do anything in client side.
If we want to do something on the client side, we can only call it through Javascript under the premise of browser security.
And it's not possible to get broswer download path with javascript.
I have a winform application that is meant to call an api to login and do other things.
When I run the api (.net core 2.2) on visual studio, and try to consume it from the WinsForm, it works fine. I later published the api and hosted it on IIS. It works fine when I launch it but the WinsForm won't work with the link I got from it (localhost/powerapi/login). It doesn't give an error, just doesn't work. I tried Fiddler with it(using the link from the IIS), it worked perfectly. Why is it not working with the WinsForm??
Please help.
UPDATE
I debugged again and found this error. It actually tries to call the API but it gets an error 500: Internal Server Error. I tried it on fiddler and got same error too. This is the screenshot of the error from visual studio
What i mean by "it works well" is that the api works well when i launch it from IIS into the browser(so as to get its link which is passed into "url" in the screenshot). And by IIS i mean local machine.
Also, the winform and the api on the same server because I'm currently running them on my pc.
How do I configure SignalR to Authenticate/Authorize to a server that is must be protected by Windows Authentication. There appears to be no way to make the JavaScript Client send Credentials with the request.
Windows authentication should be handled by the browser and you should not have to do anything special. The problem is that Chrome does not seem to handle Windows Authentication correctly. There is a thread on github that contains more details.
Also, SignalR MVC 5 Websocket no valid Credentials seems still to apply as the issue is browser related (i.e. external to SignalR).
I created an out-of-the-box ASP.NET 5 application with Windows Authentication as a test. If I hit F5 and launch it in Edge, I get presented with a login prompt. If I browse to an application on an internal web server that requires Windows Authentication, it works fine.
Is there something specific I need to do in order to be able to debug web application with Windows Authentication from localhost?
EDIT: The same application works fine in IE11 and other browsers. This is Edge 25.10586.0.0.
I am developing a Windows phone 8 application in which i am using the nuget package to create some soap requests to a web service As far as "http" concerns everything runs properly, but in order to use https i need to use a custom certificate which when i installed on the windows phone device the IE could see the https website just fine.
So the question is:
Why my HttpClient inside the application doesnt recoqnize it and what do i need to do to access it?
Is that even possible?