+julien, in case he's more familiar with ESP's different JWT audience (some docs <https://cloud.google.com/endpoints/docs/grpc/using-service-to-service-authentication-grpc#make_an_authenticated_grpc_call> )
On Wed, Aug 30, 2017 at 1:57 PM, <[email protected]> wrote: > even if we set domain name the audience would look like https:// > {domain_name}/reporter.Reporter. however, the ESP would expect the > audience to be "https://reporter.endpoints.{projectid}.cloud.goog";. are > we missing something here? > It sounds like ESP needs to be fixed. JWT with gRPC is "defined" to use an audience of https://{domain_name}/{service_name}. Besides the audience problem, we have a bigger issue to make a gRPC client > on AppEngine. The problem is ManagedChannelBuilder is not supported on > AppEngine restricted environment. Do you know if > https://cloud.google.com/endpoints/docs/grpc/transcoding is the right way > to go. something like we build a HTTP/JSON request on AppEngine to call a > gRPC backend. > I just responded to that part in another email. -- 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/CA%2B4M1oNAPKvO6vXu4kXYqZq%3D5CvHb8Bvwb6X-j97EeWVVV_vGA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
