Certificate Problems with letsencrypt
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I can't really tell If I have done something wrong, but it seems to be a problem with an intermediate certificate in the chain of letsencrypt.
So I am using keycloak, with an letsencrypt certificate and I am getting the following error:
["ERROR","2024-10-19T09:13:27.030Z","CHALLENGE_RESPONSE_ACTION_ERROR",{"error":{"stack":"Error: unable to verify the first certificate\n at TLSSocket.onConnectSecure (node:_tls_wrap:1674:34)\n at TLSSocket.emit (node:events:519:28)\n at TLSSocket._finishInit (node:_tls_wrap:1085:8)\n at ssl.onhandshakedone (node:_tls_wrap:871:12)","message":"unable to verify the first certificate","code":"UNABLE_TO_VERIFY_LEAF_SIGNATURE"}}]
A search suggested this package to be installed and executed: [https://git.coolaj86.com/coolaj86/ssl-root-cas.js](https://git.coolaj86.com/coolaj86/ssl-root-cas.js)
(for testing purposes one can set: export NODE_TLS_REJECT_UNAUTHORIZED="0")
But I can't really tell where and how to incorporate it.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository file, test, or entry point. Start by reproducing the Keycloak connection with the reported certificate-chain error and tracing the SSO plugin’s Node.js connection path; done means identifying a supported way to handle the intermediate certificate and verifying that the connection succeeds without disabling TLS verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100