Thanks for the reply. Just found this proposed gRPC, which looks fantastic. Will follow along there: https://github.com/grpc/proposal/pull/98
On Tuesday, January 21, 2020 at 10:12:36 AM UTC-8, [email protected] wrote: > > ALTS will be stable API soon. It will be supported and available for use > if you are running on GCP. However, ALTS is by design for GCP only. > > If you want to run outside GCP, you can use TLS. We have new > TlsCredentials API in grpc c++, which supports SPIFFE. > > On Tuesday, January 21, 2020 at 9:54:18 AM UTC-8, Cyrus Katrak wrote: >> >> I'm investigating the option space for securing the authenticity and >> privacy of gRPC transport connections in a service oriented architecture >> running outside of GCP. >> >> I've narrowed in on a technical solution that looks a lot like the >> marriage of SPIFFE and ALTS, with some necessary differences. Other threads >> in this mailing list seem to suggest that despite the ALTS implementation >> being included in the open source grpc repos, it remains specific to >> Google, experimental, and unsupported. >> >> I wanted to ask and understand: >> - The level of interest from the community of having a relatively open >> and extensible identity / authenticity / confidentiality solution for grpc. >> - What if anything is already underway in the community along these lines. >> - What Google's roadmap for ALTS+gRPC is. >> >> Thanks. >> > -- 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/4c00cce2-d442-43b4-b799-5ba9efea9375%40googlegroups.com.
