How to disable cert validation?

[cbluth]

Please see here: arangodb/kube-arangodb#239

I am running arangodb in kubernetes using this: https://github.com/arangodb/kube-arangodb
I my arangojs client cant validate the certificate, even if I do this:

kubectl get secret arango-cluster-ca -ojsonpath='{.data.ca\.crt}' | base64 -d > arango.ca.pem

and then:

agentOptions: {
  ca: [
    fs.readFileSync('arango.ca.pem')
  ]
}

I am getting this error when trying to connect to a kube-arango cluster:

{ Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: arangodb.example.com. is not in the cert's altnames: DNS:arango-cluster.platform.svc, DNS:arango-cluster-coordinator-3sjtn29l.arango-cluster-int.platform.svc
    at Object.checkServerIdentity (tls.js:225:17)
    at TLSSocket.onConnectSecure (_tls_wrap.js:1046:27)
    at TLSSocket.emit (events.js:127:13)
    at TLSSocket._finishInit (_tls_wrap.js:633:8)
  reason: 'Host: arangodb.example.com. is not in the cert\'s altnames: DNS:arango-cluster.platform.svc, DNS:arango-cluster-coordinator-3sjtn29l.arango-cluster-int.platform.svc',
  host: 'arangodb.example.com',
  cert: 
   { subject: { O: 'ArangoDB', CN: 'arango-cluster.platform.svc' },
     issuer: { O: 'ArangoDB', CN: 'arango-cluster Root Certificate' },
     subjectaltname: 'DNS:arango-cluster.platform.svc, DNS:arango-cluster-coordinator-3sjtn29l.arango-cluster-int.platform.svc',
     valid_from: 'Aug 16 14:31:21 2018 GMT',
     valid_to: 'Dec  3 08:31:21 2018 GMT',
     fingerprint: '3D:82:93:97:7A:45:D2:A4:95:6E:A5:02:53:DC:19:EF:F7:95:21:4D',
     ext_key_usage: [ '2.5.29.37.0', '1.3.6.1.5.5.7.3.1' ],
     serialNumber: 'BC00A4C6BF9F9CDED318D088A72FB97D',
     raw: <Buffer 30 82 02 20 30 82 01 c5 a0 03 02 01 02 02 11 00 bc 00 a5 c6 bf 9f 9c de d3 18 d0 88 b7 2f b9 7d 30 0a 06 08 2a 86 38 ce 3d 04 03 02 30 3d 31 11 30 0f ... > },

How can I turn off cert hostname validation in arangojs?
Is it possible to deploy kube-arango without a certificate?

[pluma]

After some experimenting it seems this can easily be done using the rejectUnauthorized: false agent option. The Node documentation doesn't mention that this option exists for agents, but it seems to work just fine.

However note that this is extremely insecure. It's better to use a proper self-signed certificate.

[OKNoah]

I have set rejectUnauthorized but still get Error: self signed certificate in certificate chain. Could be my own ORM that's not passing that along. I'm trying to connect my API to a local ArangoDB so I don't think it's so relevant to have authorization?

[nimalankarthik]

For anyone that still gets the above error after setting rejectUnauthorized: false, setting process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0"; before the arango import on top of the page fixes the issue.