Add support for mTLS #235
Add support for mTLS #235
Conversation
🦋 Changeset detectedLatest commit: 041a7c5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
packages/agent-base/src/index.ts
Outdated
| servername: string | undefined, | ||
| opts: tls.ConnectionOptions, | ||
| socket?: net.Socket, |
There was a problem hiding this comment.
Seems weird to me that socket is optional. Also, let's make it the first parameter:
| servername: string | undefined, | |
| opts: tls.ConnectionOptions, | |
| socket?: net.Socket, | |
| socket: net.Socket, | |
| servername: string | undefined, | |
| opts: tls.ConnectionOptions, |
There was a problem hiding this comment.
The reason it was optional was that pac-proxy-agent calls tls.connect without providing a socket. I've made your suggested changes and reverted the changes to pac-proxy-agent for now. Let me know how you would like to proceed in that regard.
There was a problem hiding this comment.
I see. How about if we do something like this in pac-proxy-agent?
socket = net.connect(opts);
if (secureEndpoint) {
const servername = opts.servername || opts.host;
socket = this.upgradeSocketToTls(
socket,
servername,
opts
);
}
There was a problem hiding this comment.
@mg-dd Did this piece of feedback get addressed? I don't see any change in pac-proxy-agent so it looks like this still needs to be done?
|
@mg-dd Great PR! I need something similar, do you need any help pushing this over the finish line? |
|
@TooTallNate this is ready for another look. The only open question is how you would like to handle the TLS connection in |
|
Hi, any news on this? I also need this feature. |
|
Any news on this? |
|
@TooTallNate: Would love to see this feature in the proxy agents. Is there anything left to do? |
|
HI, any update about this PR ? 💯 |
|
Thank you soo much for maintaining this awesome project ! |
|
can we move forward on this? what is missing? |
|
Thank you for this PR ! 🙏 🙏 |
|
we are using a patch of this pull request in production and it is working well |
|
Hello, is there news about this ? We need it ! :) @TooTallNate |
|
Any plans to get it merged? |
|
This would be really helpful. |
…proxy With this change, we have update the Apple Pay Merchant Validation implementation in order to use `hpagent` and `axios` in the presence of an egress proxy, as it's the case on our AWS environments. This is needed because we want to remove the use of `requestretry`, however `axios` has a problem preventing it from working with an egress proxy[1]. For this reason, we need to use an HttpsProxyAgent with it. We would want to use `https-proxy-agent`, however it has its own problem[2]. While we wait for these issues to be fixed, we can use `hpagent` which has been tested and works well with an egress proxy. Further information in the JIRA ticket[3]. [1] axios/axios#4531 [2] TooTallNate/proxy-agents#235 [3] https://payments-platform.atlassian.net/browse/PP-12853 Co-authored-by: Jonathan Harden <jonathan.harden@digital.cabinet-office.gov.uk> Co-authored-by: Dominic Belcher <dominic.belcher@digital.cabinet-office.gov.uk> Co-authored-by: Marco Tranchino <marco.tranchino@digital.cabinet-office.gov.uk>
With this change, we have update the Apple Pay Merchant Validation implementation in order to use `hpagent` and `axios` in the presence of an egress proxy, as it's the case on our AWS environments. This is needed because we want to remove the use of `requestretry`, however `axios` has a problem preventing it from working with an egress proxy[1]. For this reason, we need to use an HttpsProxyAgent with it. We would want to use `https-proxy-agent`, however it has its own problem[2]. While we wait for these issues to be fixed, we can use `hpagent` which has been tested and works well with an egress proxy. Further information in the JIRA ticket[3]. [1] axios/axios#4531 [2] TooTallNate/proxy-agents#235 [3] https://payments-platform.atlassian.net/browse/PP-12853 Co-authored-by: Jonathan Harden <jonathan.harden@digital.cabinet-office.gov.uk> Co-authored-by: Dominic Belcher <dominic.belcher@digital.cabinet-office.gov.uk> Co-authored-by: Marco Tranchino <marco.tranchino@digital.cabinet-office.gov.uk>
With this change, we have update the Apple Pay Merchant Validation implementation in order to use `hpagent` and `axios` in the presence of an egress proxy, as it's the case on our AWS environments. This is needed because we want to remove the use of `requestretry`, however `axios` has a problem preventing it from working with an egress proxy[1]. For this reason, we need to use an HttpsProxyAgent with it. We would want to use `https-proxy-agent`, however it has its own problem[2]. While we wait for these issues to be fixed, we can use `hpagent` which has been tested and works well with an egress proxy. Further information in the JIRA ticket[3]. [1] axios/axios#4531 [2] TooTallNate/proxy-agents#235 [3] https://payments-platform.atlassian.net/browse/PP-12853 Co-authored-by: Jonathan Harden <jonathan.harden@digital.cabinet-office.gov.uk> Co-authored-by: Dominic Belcher <dominic.belcher@digital.cabinet-office.gov.uk> Co-authored-by: Marco Tranchino <marco.tranchino@digital.cabinet-office.gov.uk>
This PR fixes two issues:
#194
#234
The background is that the TLS connection established by the proxy agents do not add the required parameters for mTLS / self-signed CAs. This PR adds a way to provide these parameters. The general approach was taken from the feedback from this PR: https://github.com/TooTallNate/proxy-agents/pull/195/files
ptal @TooTallNate