Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please support ChannelCredentials #1396

Open
cccRaim opened this issue Jan 6, 2025 · 3 comments
Open

Please support ChannelCredentials #1396

cccRaim opened this issue Jan 6, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@cccRaim
Copy link

cccRaim commented Jan 6, 2025

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

@cccRaim cccRaim added the enhancement New feature or request label Jan 6, 2025
@timostamm
Copy link
Member

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
Copy link
Author

cccRaim commented Jan 7, 2025

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

@timostamm
Copy link
Member

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants