Optional mechanisms are available for clients to To authenticate the server, and to encrypt all the data exchanged between SSL/TLS: gRPC has SSL/TLS integration and promotes the use of SSL/TLS.The following authentication mechanisms are built-in to gRPC: Necessary authentication information as Credentials when creating a channel or GRPC also provides a simple authentication API that lets you provide all the Mechanisms - SSL/TLS with or without Google token-based authentication - or youĬan plug in your own authentication system by extending our provided code. GRPC is designed to work with a variety of authentication mechanisms, making itĮasy to safely use gRPC to talk to other systems. Base case - No encryption/authorizationĪn overview of gRPC authentication, including built-in auth mechanisms, and how to plug in your own authentication systems.Īn overview of gRPC authentication, including built-in auth mechanisms, and how to plug in your own authentication systems.Authenticate with Google using Oauth2 token (legacy approach).Base case - No encryption/authentication.With server authentication SSL/TLS and a custom header with token.Authenticate with Google using an Oauth2 token.
Base case - No encryption or authentication.
0 kommentar(er)
