Secure access about i-analyzer HOT 6 CLOSED

Currenty, on the Acc & Prod server (ianalyzer(.acc).hum.uu.nl) there is a Apache proxy configured that redirects Angular calls to ES. This is not a permanent solution because anyone could approach ES.

Note, however, that as long as reaching ES is configured like this, creating an index does not work, because the ES_HOST setting is not set to 'localhost' and, for the proxy to work, ES_PORT should be an empty string.

from i-analyzer.

Could perhaps use proxy settings for this (similar to how this is done for the api)?

from i-analyzer.

What do you mean by "proxy settings"?

from i-analyzer.

This file: https://github.com/UUDigitalHumanitieslab/I-analyzer/blob/develop/web-ui/proxy.conf.json You can set the node server to proxy calls directly to another one, based on some address prefix. I believe the same could also be done using Docker. This way you do not need cross server requests from the client, because they are still just going directly to the server.

from i-analyzer.

Oh, right. Yes, I have done that before with Microcontact. It can be nice to make the software such that the ES index can also be on a different server, though. ES indexes are sometimes heavy.

from i-analyzer.

See issue #80 .

from i-analyzer.