sense with shield secured cluster

[bilsch]

Checking in on the state of sense when operating on a secured cluster. We are using shield for authentication/authorization and also SSL.

It looks like sense is firing http requests from nodejs / kibana level. Are the browser credentials passed in?

Also it looks like using ssl connections is failing - Client request error: certificate not trusted. Which is interesting given openssl verification does work.

openssl s_client output:

SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES128-SHA
    Session-ID: 56B37CC6693CC0428D3C932B2AF144C0D523F99EA95A2D28EE400222B701F962
    Session-ID-ctx:
    Master-Key: 43E7F19BAF417E551240B3DFA4F24C9A2CEAF6414243E1E08E4FA2E448366A95A478F24BFCD2CDDD7BD1D23405CBA6B8
    Key-Arg   : None
    Krb5 Principal: None
    PSK identity: None
    PSK identity hint: None
    Start Time: 1454603462
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)

---

[vicvega]

👍
same error here

[jakommo]

Related to #69 ?

[onemark]

I get the "Client request error: self signd certificate" error again using sense-2.0.0-beta5 on Kibana 4.5.0, adding " rejectUnauthorized: false" in the index.js does not help anymore. I copied the complete index.js from the older version (including the rejectUnauthorized line) to the new version which is working.