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

Getting jwks Failure: Error: SSL Error: SELF_SIGNED_CERT_IN_CHAIN #67

Closed
barathank opened this issue Nov 13, 2018 · 3 comments
Closed
Labels
closed:stale Issue or PR has not seen activity recently

Comments

@barathank
Copy link

When trying to get the JWT keys to validate a token, the request fails when the environment has a self-signed cert in the chain behind enterprise proxy.
jwks Fetching keys from 'https://authserver/oauth2/default/v1/keys' +0ms
jwks Failure: Error: SSL Error: SELF_SIGNED_CERT_IN_CHAIN
at Request.onRequestResponse (node_modules/request/request.js:952:24)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:551:21)
at HTTPParser.parserOnHeadersComplete (_http_common.js:115:23)
at TLSSocket.socketOnData (_http_client.js:440:20)
at emitOne (events.js:116:13)
at TLSSocket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11) +181ms
Error: SSL Error: SELF_SIGNED_CERT_IN_CHAIN
at Request.onRequestResponse (node_modules/request/request.js:952:24)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:551:21)
at HTTPParser.parserOnHeadersComplete (_http_common.js:115:23)
at TLSSocket.socketOnData (_http_client.js:440:20)
at emitOne (events.js:116:13)
at TLSSocket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)

@sonman1
Copy link

sonman1 commented Jan 14, 2019

Have seen the same issue. No new insights or debug - same as noted here. Has anyone discovered a work around?

@cconcannon
Copy link
Contributor

I just opened a PR which will allow resolution of this issue by allowing pass-through of (among other things) a private certificate authority chain via the request options agentOptions property to the request library configuration

#84

@stale
Copy link

stale bot commented Oct 26, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇‍♂️

@stale stale bot added the closed:stale Issue or PR has not seen activity recently label Oct 26, 2019
@stale stale bot closed this as completed Nov 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed:stale Issue or PR has not seen activity recently
Projects
None yet
Development

No branches or pull requests

3 participants