Please support ChannelCredentials

[cccRaim]

Is your feature request related to a problem? Please describe.
My server need pinned CA certificates, but I don't know how to set that in connect-es.

Describe the solution you'd like
support ChannelCredentials

Please specify whether the request is for Connect for Web or Connect for
Node.js.

Describe alternatives you've considered
just use @grpc/grpc-js, but no proto types

Additional context

[timostamm]

Connect aims for slim implementations on top of the platform's HTTP stack. We want servers to be able to serve RPC alongside other HTTP routes. Supporting ChannelCredentials would be detrimental to this goal.

You are looking for options to http2.createSecureServer. See this example on nodejs.org, and the documentation for TLS.

[cccRaim]

No, I'm client, so can client support this?

[timostamm]

For clients, you can specify HTTP/2 connection options with nodeOptions when creating a transport:

createGrpcTransport({
  baseUrl: "...",
  nodeOptions: {},
});

[chrispine]

I'm going to go ahead and close this one, but let us know if there's anything else you need

[phsultan]

No need to support ChannelCredentials. This worked in our case:

createGrpcTransport({
  nodeOptions: {
    secureContext: tls.createSecureContext({
      ca: process.env.RPC_TLS_CA,
    }
  },
})

The RPC_TLS_CA is an environment variable containing the certificate, but I you can extract it from a file as well.

Thanks for the great work on connectprc!

[timostamm]

As another alternative, we put up a PR to support @bufbuild/protobuf with the grpc-tools package: grpc/grpc-node#3005