This thing is that ssl certificate erros will happen *before *the RPC reaches your code(ie the code for your routes), so you can't "send back" any high level error. You have to handle those in your client.
[below is not a good idea] You could also disable the server ssl verification(eg GRPC_SSL_REQUEST_CLIENT_CERTIFICATE_BUT_DONT_VERIFY), and then do whatever you want in you custom AuthMetadataProcessor. On Friday, October 5, 2018 at 6:58:49 PM UTC+2, AK wrote: > > For example, when SSL certificate expires or its verification fails gRPC > call returns UNAVAILABLE (code 14). The actual error either goes to console > or a log file, if it was set. However, that is not visible to clients. The > user doesn't understand what went wrong from failed connection error. How > to communicate more information about the errors back to client? I am using > C++ server and client programs. > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/de393ff0-921e-42a7-858b-e4f6d1be3acf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
