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

Add support for enterprise SSL interception certificates #2902

Closed
mungojam opened this issue May 10, 2019 · 9 comments
Closed

Add support for enterprise SSL interception certificates #2902

mungojam opened this issue May 10, 2019 · 9 comments

Comments

@mungojam
Copy link

Our company uses SSL interception with their own certificate which is trusted by windows.

When using aws-cdk, this leads to the inevitable error as node doesn't natively use windows cert store:

? Bootstrapping environment ###/eu-west-1...
? Environment ###/eu-west-1 failed bootstrapping: Error: self signed
certificate in certificate chain
at TLSSocket.onConnectSecure (_tls_wrap.js:1260:34)
at TLSSocket.emit (events.js:196:13)
at TLSSocket.EventEmitter.emit (domain.js:471:20)
at TLSSocket._finishInit (_tls_wrap.js:737:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:569:12) {
message: 'self signed certificate in certificate chain',
code: 'NetworkingError',
region: 'eu-west-1',
hostname: 'cloudformation.eu-west-1.amazonaws.com',
retryable: true,
time: 2019-05-06T16:46:50.195Z
}
self signed certificate in certificate chain

With our own node tools, we have circumvented this by using either syswide-cas or win-ca. VS Code recently integrated a win-ca fork as well so that no longer has the problem. This hasn't been possible with cdk as I don't seem able to inject the win-ca import early enough I think.

Please consider adding an integrated solution/option so that we can use CDK internally without having to mess with global environment variables.

I've worked around it for now setting the NODE_EXTRA_CA_CERTS environment variable to a snapshot of the certs extracted with win-ca but that's not a sustainable approach and would be messy to set up for other devs.

@nmussy
Copy link

nmussy commented Sep 19, 2019

Should this issue be brought to the AWS SDK for Node repo? All requests to the AWS are made through the SDK library AFAIK

@mungojam
Copy link
Author

that's a good point, happy for somebody from aws move it over.

@nmussy
Copy link

nmussy commented Sep 20, 2019

I'm not sure that's possible. You can just open another issue there and reference this one as your use-case.

@mungojam
Copy link
Author

@nmussy
Copy link

nmussy commented Sep 22, 2019

TIL! Thanks

@SomayaB SomayaB transferred this issue from aws/aws-cdk Oct 11, 2019
@ajredniwja
Copy link
Contributor

ajredniwja commented Oct 14, 2019

Hey @mungojam,

It doesn't seem to be a an issue with the JavaScript SDK.

If you still feel it is an issue with the JS-SDK then It'd be great if you can follow the issue template so that we can have more information about the issue.

@ajredniwja ajredniwja added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Oct 29, 2019
@mungojam
Copy link
Author

I probably won't get a chance to follow up on this as we've now moved to terraform rather than CDK. Happy to close unless others can follow up with reproductions

@no-response no-response bot removed the closing-soon This issue will automatically close in 4 days unless further comments are made. label Oct 30, 2019
@ajredniwja
Copy link
Contributor

@mungojam,

Thank-you for the update, I will go ahead and close the issue, if anyone has further questions, please re-open or create a new issue.

@lock
Copy link

lock bot commented Nov 11, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants