-
-
Notifications
You must be signed in to change notification settings - Fork 162
Description
Summary
I'm on a company VPN, trying to make a leapp integration for a customer environment. Using the browser, I can sign in (it requires having https in the URL, but it returns as "insecure" because of the self signed cert) through the AWS SSO. However, using the Leapp integration causes nothing to pop up, even when browser is selected. Using the CLI, I can now see why that is. Error code is written below.
Version
Leapp Version 0.13.4
Expected Response:
I understand why insecure connections may be blocked, but it seems to fail without displaying an error to the user (unless using the CLI), and it would be nice to have an --insecure override if there's not other way of resolving this. How might I get this to connect for now?
CLI Response (leapp integration login):
node:events:491
throw er; Unhandled 'error' event
^
{
Error: self signed certificate in certificate chain
at TLSSocket.onConnectSecure (node:_tls_wrap:1534:34)
at TLSSocket.emit (node:events:513:28)
at TLSSocket.emit (node:events:489:12)
at TLSSocket._finishInit (node:_tls_wrap:948:8)
at ssl.onhandshakedone (node:_tls_wrap:729:12)
Emitted 'error' event on Writable instance at:
at eventHandlers.<computed> (/usr/local/lib/node_modules/@noovolari/leapp-cli/node_modules/follow-redirects/index.js:14:24)
at ClientRequest.emit (node:events:513:28)
at ClientRequest.emit (node:events:489:12)
at TLSSocket.socketErrorListener (node:_http_client:481:9)
at TLSSocket.emit (node:events:513:28)
at TLSSocket.emit (node:domain:489:12)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
code: 'SELF_SIGNED_CERT_IN_CHAIN'
}
Node.js v18.7.0
Desktop:
- OS: MacOS Monterey
- OS Version 12.5
- Leapp Version 0.13.4