Allow mTLS connections to ES

[tmegow]

While dismissing the feature request described in Issue #32 as a Bug Report, half the Feature Request was ignored.

TLS
—
I stupidly thought the -k option on curl would make the request transparent but I should have provided more clarifying info. You’ve offered that there is no way to supply overridden/custom certs in a Chrome, Edge, Firefox extensions. I did some simple research (as a green browser extensions dev) on the topic and I see these extension API features, do these allow supplying custom certs? If feasible, please allow us to supply self-signed certs using these extension features and allow us to connect to ES using self-signed certs.
WebExtensions API - SecurityInfo Chrome Extensions API - certificateProvider

mTLS
—
See xpack.security.transport.ssl.client_authentication and xpack.security.http.ssl.client_authentication

Does ElasticVue allow mTLS using client certificates? If not please allow us to connect to ES using x509 certs for authentication.

[cars10]

Hey, sorry for overseeing your question regarding mTLS / client certificates in general. I have some questions regarding this feature request:

1. I am not quite sure how these certificates are used. Would you expect the browser to show a built-in popup where you can select a preinstalled certificate our do you need a file selection button to "upload" the actual certificate from your local filesystem?
2. Did you try the third solution i proposed in #32? It would be interesting to know if this could (temporarily) solve the problem.

Thanks!

[cars10]

Close for now, because I am still not sure how your setup looks like and what exact problem you want to solve. Please feel free to reopen this issue with additional details (and an example setup if possible).