Configuring the gRPC client and server for unencrypted communication

Before we start talking about the process of securing gRPC endpoints with a custom certificate, we will cover the base case – that is, how to set up your application to run without any such certificate. This is useful for real-life scenarios, as even though gRPC was originally intended to primarily run over TLS, there are situations where using a certificate just adds unnecessary overhead. For example, if a gRPC endpoint represents a microservice that is only ever hosted on your internal network and is never exposed to the public internet, encrypting the communication within it (and going through the entire process of obtaining a valid certificate from a certification authority) might not be necessary.

Likewise, it's not necessary to use encryption when you are writing the software on your development machine. Even though a project created from the gRPC service .NET template will have encryption enabled...