gRPC custom client/server certificates & grpc channel options

[Ten0]

Is your feature request related to a problem? Please describe.
Can't use insomnia for gRPC because we authenticate to our gRPC services using a custom PKI, and need to pass particular additional options to the client builder (grpc.ssl_target_name_override, grpc.keepalive_time_ms,...).
We are stuck to BloomRPC because of this, and bloom doesn't work super well (lack of ergonomics, environment management, and diverse bugs).

Describe the solution you'd like
Being able to configure, ideally by workspace with overrides per environment, the set of CA key, client certificate, client key and additional options.

This is where this should hit in the code:

insomnia/packages/insomnia-app/app/network/grpc/index.js

Lines 26 to 30 in f27cd5f

	const credentials = enableTls ? grpc.credentials.createSsl() : grpc.credentials.createInsecure();
	console.log(`[gRPC] connecting to url=${url} ${enableTls ? 'with' : 'without'} TLS`);
	const Client = grpc.makeGenericClientConstructor({});
	return new Client(url, credentials);

becoming in effect:

 const credentials = enableTls ? grpc.credentials.createSsl('ca file content', 'private key file content', 'cert chain file content') : grpc.credentials.createInsecure(); 
  
 console.log(`[gRPC] connecting to url=${url} ${enableTls ? 'with' : 'without'} TLS`); 
 const Client = grpc.makeGenericClientConstructor({}); 
 return new Client(url, credentials, {'grpc.keepalive_time_ms': 12, 'grpc.ssl_target_name_override': 'value' /* and other custom settings*/});

(note that it looks like gRPC Core does not receive the options in the same way if they are integers or strings, so this may matter. I'd be very happy with providing these as a JSON, similarly to what's done with the environments.)

[Ten0]

For anyone interested I've created some form of dirty patch that provides this functionality.
Feel free to PR a better integration :)

https://github.com/Ten0/insomnia/commits/grpcs_certificates

[brianjobling]

Hello @Ten0 this is exactly the feature I was looking for as I want to pass the ssl_target_name_override. I have looked at the code, but don't know where I am meant to put these definitions - can you help?

[Ten0]

You want to put grpc.ssl_target_name_override in the last options of the client building as hinted here, so it needs to be put as:

{
    "__grpc_additional_client_options": {
        "grpc__ssl_target_name_override": "value"
    }
}

in the insomnia environment. (1, 2).

[mdeville]

The SSL certificates support to have been added here but not the custom client gRPC options