-
Notifications
You must be signed in to change notification settings - Fork 123
[Bug] TLS server name override not respected #1681
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
Comments
Yes please :) This is blocking us from taking our app to production where we only want to use PrivateLink and not go through the internet |
Can anyone please let us know what is the status here? |
Very sorry for the delay. I was honestly under the impression that our support team had already provided you a suitable workaround through our Zendesk portal, but this might have been a different conversation. My bad. The current workaround is to add this dependency to your own package.json:
This will get Client connections through Private Link working properly. |
Thank you @mjameswh , any estimation on getting a real fix? |
There are actually two solutions coming up:
Any of these two will resolve the problem you are facing. I expect both to be available in the next few days. |
What are you really trying to do?
Setting a TLS server name override in client connection connect
Describe the bug
When setting a server name override in client connection, the TLS server name is mishandled by
grpc-js
library and ends up overridden with the address providedMinimal Reproduction
Environment/Versions
TS SDK 1.11.7
Additional context
grpc-js servername override
The text was updated successfully, but these errors were encountered: