UNAVAILABLE is the right status code in this situation, but the error message returned along with that status code should provide more useful information. Fixing this will require some deep plumbing changes, so I don't know if it will happen anytime soon, but I have filed the following bug to track it:
https://github.com/grpc/grpc/issues/22885 On Wednesday, May 6, 2020 at 7:15:56 AM UTC-7 [email protected] wrote: > is there a way to return ssl error to client, i am getting > UNAVAILABLE(code 14) when client certificate validation fails in server. > > > On Saturday, 6 October 2018 03:33:12 UTC+5:30, AK wrote: >> >> I was in exact same situation. In my opinion, client should be notified >> of what caused the server to throw an error. >> >> On Friday, October 5, 2018 at 2:22:36 PM UTC-7, Benjamin Krämer wrote: >>> >>> Just had the same problem at a customer site and costed me an hour to >>> find out that I used the wrong certificate files. Had to enable logging and >>> check the errors in there to see the SSL_VERIFY_FAILED. The channel itself >>> only went to TransientFailure. Using C#, so not much look their either. >>> >> -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/8bfb6858-4fae-45cf-8289-493a0c0e8f39%40googlegroups.com.
