WebApiProxy.CSharp configuration should have attribute allowUntrustedSsl #35

Activity

1. faniereynders commented on Jan 29, 2015

   

   faniereynders

   on Jan 29, 2015

   Member

   More actions

   Hi @pauliusg have you found a workaround for this?
2. pauliusg commented on Jan 29, 2015

   

   pauliusg

   on Jan 29, 2015

   Author

   More actions

   Hi,

   Currently I have 2 endpoints (http and https) and later I can set the right one from code:
   WebApi.Proxies.Configuration.PosWebApiProxyBaseAddress = ...

   Also for client I have to provide my requests handler:

   var handler = new WebRequestHandler();
   handler.ServerCertificateValidationCallback += (sender, certificate, chain, sslPolicyErrors) => true;
   
   using (var client = new UpdateProcessedImageClient(handler))
   {
   
   }

   Custom handler is not a problem at all, but problem if third party WebAPI provider has only https endpoint with self-signed certificate. I am very happy that my third party provides both :)
3. faniereynders commented on Jan 29, 2015

   

   faniereynders

   on Jan 29, 2015

   Member

   More actions

   You can also wrap your the handler.ServerCertificateValidationCallback(...) call in conditional compilation directives like DEBUG for example in your development environment
4. pauliusg commented on Jan 29, 2015

   

   pauliusg

   on Jan 29, 2015

   Author

   More actions

   Thing is, that my third party will have self-signed cert even in production. I don't like that but I can't change that.

   As I said, I have my workarounds, but it would be nice to have attribute in config to allow generate client from server which has invalid SSL cert.
5. wolfen351 commented on Jan 16, 2016

   

   wolfen351

   on Jan 16, 2016

   Collaborator

   More actions

   Is the issue the generation or runtime? Reading between the lines it looks like generation time, if so we could just add the config setting as you describe..
6. faniereynders

   added

   enhancement

   proposal

   on Jan 17, 2016
7. pauliusg commented on Jan 18, 2016

   

   pauliusg

   on Jan 18, 2016

   Author

   More actions

   Yes, issue is only in the generation.
8. faniereynders commented on Jan 19, 2016

   

   faniereynders

   on Jan 19, 2016

   Member

   More actions

   So if I understand it correctly, the proxy endpoint is over HTTPS and the generation fails on the development machine because there's no self-signed certificate? Also, if you're saying two endpoints, do you mean one for development (using HTTP) and one for production (using HTTPS)?
9. pauliusg commented on Jan 20, 2016

   

   pauliusg

   on Jan 20, 2016

   Author

   More actions

   Guys you are talking about the same thing again. Currently I have no issues with my project because endpoint can be accessed by http or https, so I run generation over http and later from code I change endpoint to https also I set ServerCertificateValidationCallback to always return true.

   Issue is in client generation.

   But I think for other WebApiProxy users who have only HTTPS endpoint with self signed certificate it would be great to have attribute allowUntrustedSsl in configuration. If you don't want to implement that, please close this issue. I don't care.
10. faniereynders commented on Jan 20, 2016

    

    faniereynders

    on Jan 20, 2016

    Member

    More actions

    This issue has been discussed over and over in #79 and due to low demand and priority it was decided to not implement for now (at least). When there's more demand for this feature we could look at it again in the future. Thank you for your contribution @pauliusg! 👏
11. faniereynders

    closed this as completedon Jan 20, 2016