[JBoss JIRA] (RTGOV-345) Fine grained access to ElasticSearch
by Gary Brown (JIRA)
Gary Brown created RTGOV-345:
--------------------------------
Summary: Fine grained access to ElasticSearch
Key: RTGOV-345
URL: https://issues.jboss.org/browse/RTGOV-345
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
Building on the course grained access in RTGOV-344, this issue will enable role information associated with the user to be used to filter out information they are not permitted to view.
Some options:
a) encode the information necessary to do the filtering in the role
b) the role can be a key that is used to determine how the filtering is done
(b) would require additional administration to install the processing required to do the specific filter.
Other consideration:
(i) should the filter be applied to the query/search, to automatically limit the result
(ii) should the filter be applied to the result
Need to consider various use cases vs performance to see which approach will generally be better.
--
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
10 years, 5 months
[JBoss JIRA] (RTGOV-344) Course grained access to ElasticSearch
by Gary Brown (JIRA)
Gary Brown created RTGOV-344:
--------------------------------
Summary: 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
10 years, 5 months
[JBoss JIRA] (RTGOV-343) EPN to store activity events and situations in ElasticSearch
by Gary Brown (JIRA)
Gary Brown created RTGOV-343:
--------------------------------
Summary: EPN to store activity events and situations in ElasticSearch
Key: RTGOV-343
URL: https://issues.jboss.org/browse/RTGOV-343
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
Standard EPN deployment for storing activity events and situations in ElasticSearch.
The ActivityUnit (minus the events) should be stored as one type, the ActivityType derived objects as another, and the situations as their own type.
Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?
--
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
10 years, 5 months
[JBoss JIRA] (RTGOV-342) ElasticSearch Event Processor implementation
by Gary Brown (JIRA)
Gary Brown created RTGOV-342:
--------------------------------
Summary: ElasticSearch Event Processor implementation
Key: RTGOV-342
URL: https://issues.jboss.org/browse/RTGOV-342
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
The EventProcessor configuration should be provided with:
a) Index name
b) Type name
c) MVEL expression for obtaining id from the event
NOTE: Also need to be able to indicate that a random id should be used - possibly if mvel expression is not defined?
If REST call does not succeed, then throw exception to prompt a retry of the event.
--
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
10 years, 5 months
[JBoss JIRA] (RTGOV-341) Enable ActivityStore implementation to be specified in configuration
by Gary Brown (JIRA)
Gary Brown created RTGOV-341:
--------------------------------
Summary: Enable ActivityStore implementation to be specified in configuration
Key: RTGOV-341
URL: https://issues.jboss.org/browse/RTGOV-341
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
Need to be able to specify the activity store implementation to be used in a JEE environment. The various implementations will be bundled in the overlord-rtgov.war, and therefore we need a way to distinguish which implementation to use.
--
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
10 years, 5 months
[JBoss JIRA] (RTGOV-340) Message tab readonly when no resubmit provider
by Gary Brown (JIRA)
Gary Brown created RTGOV-340:
--------------------------------
Summary: Message tab readonly when no resubmit provider
Key: RTGOV-340
URL: https://issues.jboss.org/browse/RTGOV-340
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Components: User Interface
Reporter: Gary Brown
Assignee: Gary Brown
Currently when the 'Situation Details' page is selected for a particular situation, the Message tab is displayed with an editable version of the message content.
Enhance this functionality in the following way: Only make the message editable, and show the 'resubmit' button, if the 'resubmit' property is found with a supported provider value.
In future, additional checks will be that the user has permission to view and/or resubmit this message.
--
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
10 years, 5 months
[JBoss JIRA] (RTGOV-339) Date/time range filter does not currently allow time to be specified
by Gary Brown (JIRA)
Gary Brown created RTGOV-339:
--------------------------------
Summary: Date/time range filter does not currently allow time to be specified
Key: RTGOV-339
URL: https://issues.jboss.org/browse/RTGOV-339
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Components: User Interface
Reporter: Gary Brown
Assignee: Gary Brown
Date/time filter only currently allows the date to be specified, which only allows the granularity to be at the level of days.
We need the user to be able to specify the filter down to the seconds level of granularity.
--
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
10 years, 5 months