@grpc/grpc-js : SNI is not Supported
See original GitHub issueI am using @grpc/grpc-js
(1.0.4) as a client. There is no way to set the servername
parameter anywhere when instanciating a new client via new Client()
. As a result, a server requiring SNI will return a random certificate which the client will reject if it doesn’t match what was in the address
parameter of the Client
constructor. Did I miss anything or is there actually no way of doing this properly right now ? Should something like that go in the ChannelCredentials.createSsl
or something ? Thanks.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
@grpc/grpc-js - npm
Documentation specifically for the @grpc/grpc-js package is currently not available. However, documentation is available for the grpc ...
Read more >grpc/grpc - Gitter
$ grpcurl --help -cacert string File containing trusted root certificates for verifying the server. Ignored if -insecure is specified. -cert string File ...
Read more >TLS (SSL) | Node.js v19.3.0 Documentation
SNI : Allows the use of one TLS server for multiple hostnames with different certificates. Pre-shared keys#. TLS-PSK support is available as an...
Read more >Module ngx_http_grpc_module - Nginx.org
Makes outgoing connections to a gRPC server originate from the specified local IP address with an optional port. Parameter value can contain variables....
Read more >Admin API - v3.1.x - Kong Docs
Non-printable ASCII (for example, the space character) is not allowed. ... For tls_passthrough , set snis ;; For grpc , at least one...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mbwhite A fix for that is incoming in #1486.
grpc.ssl_target_name_override
should only be used on the client side.