Using “Plaintext” Mode for Communication with the gRPC Server
In a development environment, it might be useful if data was not encrypted when first building a solution that leverages gRPC. This would allow you to develop your gRPC implementation without first having to acquire and configure any certificates needed for TLS. However, this is less secure. Integration Serverprovides a configuration parameter to set the gRPC channels to “plaintext” mode.
Set watt.server.grpc.enable.TLS to one of the following:
True. The gRPC server operates in ciphertext mode and uses TLS to encrypt data during transmission.
False. The gRPC server operates in plaintext mode in which the gRPC server does not use TLS to encrypt data and does not perform any client certificate authentication on inbound requests. Th gRPC server rejects requests with client certificate information provided in inbound requests. The value of
watt.server.grpc.clientCertRequired is ignored when gRPC channels operate in plaintext mode.
Important:
Use of TLS for data encryption is expected for gRPC. Software AG strongly recommends using TLS for gRPC communications in a production environment.