-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Support TCP microservice over TLS #6745
Labels
Comments
BorntraegerMarc
added
needs triage
This issue has not been looked into
type: enhancement 🐺
labels
Mar 24, 2021
Would you like to create a PR for this issue? :) |
I would love to create a PR 😄 I'm missing a bit the time though. Anyone else can take this one? |
Hey, I work with nestjs since two years and want to contribute to the project. If you @kamilmysliwiec want, I would try to create a PR for it? |
@daflodedeing sounds great! |
@daflodedeing Any progress? |
This was referenced Jul 11, 2021
Let's track this here #7516 |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Is your feature request related to a problem? Please describe.
In our Hybrid-Cloud environment we have some microservices running in our Cloud and some microservices running On-Premise of our customers.
Communication between the microservices is all TCP based.
Now, unencrypted traffic for internal Cloud communication might be OK. But not once the traffic goes beyond the Cloud over the public internet inside to a mission critical On-Prem service.
Describe the solution you'd like
NodeJS supports TCP sockets over TLS: https://nodejs.org/api/tls.html#tls_tls_createserver_options_secureconnectionlistener
Something similar should be implemented for NestJS.
Teachability, Documentation, Adoption, Migration Strategy
It's a new feature:
What is the motivation / use case for changing the behavior?
I'm aware of the old issue: #1056
I'm also aware of the possibility to create a custom NestJS transporter to achieve the same goal.
However this ticket is about native NestJS TLS support. Which seems a good idea to secure traffic.
The text was updated successfully, but these errors were encountered: