401 Unauthorized error
-
Hello, I do apologize if this is the incorrect forum to post. I have a file which I need to post to a remote client server. I created a .p12 key file from the client web site. Using this .p12 ket file, password information I need to post a file to the server. Using class, X509Certificate2 from namespace using System.Security.Cryptography.X509Certificates X509Certificate2. I created a simple C# console application on my laptop using VS 2010, to define the parameters to the .p12 key file, and path to the csv file to post to remote server. I keep getting "Remote Server returned error - 401 UnAuthorized Error". Is there some sort of permission issue on .net end or the client side. The client keeps stating there is no communcation problem on their end. I have been working on this code for some time now. any ideas is much, much appreciated.
-
Hello, I do apologize if this is the incorrect forum to post. I have a file which I need to post to a remote client server. I created a .p12 key file from the client web site. Using this .p12 ket file, password information I need to post a file to the server. Using class, X509Certificate2 from namespace using System.Security.Cryptography.X509Certificates X509Certificate2. I created a simple C# console application on my laptop using VS 2010, to define the parameters to the .p12 key file, and path to the csv file to post to remote server. I keep getting "Remote Server returned error - 401 UnAuthorized Error". Is there some sort of permission issue on .net end or the client side. The client keeps stating there is no communcation problem on their end. I have been working on this code for some time now. any ideas is much, much appreciated.
vanikanc wrote:
a file which I need to post to a remote client server
vanikanc wrote:
I keep getting "Remote Server returned error - 401 UnAuthorized Error".
To me, based on above statements, it looks like the request is not going through. The key created/used is not having correct password or so leading to unauthorized error. Issue wise, it might be of certificate or the way you are sending/using it to communicate. Ideally, client server must be setup to accept calls with proper certificate(having correct password) for handshake permission. Error wise, the communication is not as per expected. Talk to someone on client side, make sure you are communicating correctly and the certificate-password is valid.
Sandeep Mewara Microsoft ASP.NET MVP 2012 & 2013 [My Blog]: Sandeep Mewara's Tech Journal! [My Latest Article]: HTML5 Quick Start Web Application