[
https://issues.jboss.org/browse/RTGOV-344?page=com.atlassian.jira.plugin....
]
Gary Brown commented on RTGOV-344:
----------------------------------
Implementation: can be a servlet or jax-rs service - whichever is most appropriate. It
should use the same security as defined here:
https://github.com/Governance/rtgov/blob/master/release/jbossas/war-serve...
Last step will be to update the kibana integration to specify the location of the proxy:
https://github.com/Governance/rtgov-ui/blob/master/overlord-rtgov-ui-war/...
The war should have a context overlord-rtgov-elasticsearch
Course grained access to ElasticSearch
--------------------------------------
Key: RTGOV-344
URL:
https://issues.jboss.org/browse/RTGOV-344
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
ElasticSearch does not provide any authentication/authorization mechanism, so a proxy
service should be implemented to provide this functionality. The location of the
ElasticSearch cluster can be obtained from the rtgov properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira