--
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 grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CALtmcYME9BGvq1dJhy%3D0bWK06DRYYfQ8i_hEQ8_2ujnWwFsv7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Kerberos is strange in that it authenticates an entire connection, which is counter to HTTP semantics. It currently seems semi-incompatible with HTTP/2, or at least how to do it with HTTP/2 hasn't been specified. Thus gRPC is not currently compatible with Kerberos.
On Fri, Jul 15, 2016 at 2:48 PM, 孙佩 <sunpe...@gmail.com> wrote:
Hi GRPC experts,I am doing an experiment to replace thrift with GRPC. One blocker is security. What is the recommended way to integrate Kerberos with GRPC?ThanksPei
--
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 grpc-io+u...@googlegroups.com.