The authority is available to the channel credentials when the creds are being created. As you noticed, the authority is used to verify the identity in TLS, and allows the server to route your request .
Does this answer your question? On Wednesday, October 24, 2018 at 2:07:08 AM UTC-7, Sander Saares wrote: > > I found a comment on GitHub saying " At least with Java, using this with > TLS will require the overridden authority to still appear on your server's > cert - I believe the same is true for wrapped languages (including C#), but > if you plan to use this in production this should be verified." which might > shed some light on it. However, there remains a conflict between "only > works with Insecure" and "requires the name to be present". > > On Wed, Oct 24, 2018 at 7:50 AM <[email protected] <javascript:>> wrote: > >> I use the HTTP2 ":authority" header for routing gRPC requests from a >> nginx gateway to various gRPC servers, along the lines of >> https://github.com/grpc/grpc/issues/14900 >> >> So far I have not used any credentials but I wish to do so soon. However, >> I notice that in the documentation of the DialOptions.WithAuthority() call, >> there is the following statement: >> >> // :authority pseudo-header. This value only works with WithInsecure and >> has no >> // effect if TransportCredentials are present. >> // WithAuthority returns a DialOption that specifies the value to be >> used as the >> >> I am probably missing something obvious here but what is the relation >> between the ":authority" header and the transport credentials? Is my >> routing somehow incompatible with the use of proper channel credentials? >> >> >> Cheers, >> >> Sander >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "grpc.io" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/grpc-io/5t0BMlu4Qhk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/85b1974e-f961-4c65-9601-77ea4c2401d0%40googlegroups.com >> >> <https://groups.google.com/d/msgid/grpc-io/85b1974e-f961-4c65-9601-77ea4c2401d0%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/5e75eb6c-eca1-4a95-9aa9-8ee4a90089c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
