[
https://issues.apache.org/jira/browse/METRON-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589896#comment-16589896
]
ASF GitHub Bot commented on METRON-1665:
----------------------------------------
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/1111
Thanks for the catches Ryan.
My objective around metron-rest was to try and leave it as little changed
as possible in this effort, since the ticket is more around the ui hosts, but I
would agree that this could be cleaned up as you suggest.
On the issue of Roles, I don't think we really make the best use of roles
at present, and need a follow on to sort all that out. There is also some
debate to be had about how roles should be used. A trivial (and in my view
naive) view would be to map roles to LDAP groups. This is quite a common
approach, but is also a wrong approach, Roles are logical groups of capability,
not groups of user principals. I would like to see a follow on where we
actually define and properly apply concepts of roles to access controlled
objects in Metron, but in the short term we could definitely use the
placeholder TODO here to add a naive mapping.
> Move hosting of Alerts and Config UIs from Nodejs to Spring Boot
> ----------------------------------------------------------------
>
> Key: METRON-1665
> URL: https://issues.apache.org/jira/browse/METRON-1665
> Project: Metron
> Issue Type: Sub-task
> Reporter: Simon Elliston Ball
> Assignee: Simon Elliston Ball
> Priority: Major
>
> The current UIs are served up by very lightweight nodejs applications, which
> serve the static bundle files produced by the angular build process, and
> proxies the rest api.
> The proposal is to use a spring boot application, allowing us to harmonise
> the security implementation across the UI static servers and the REST layer,
> and to provide a routing platform for later microservices.
> The UIs currently proxy to the REST API to avoid CORS issues, this will be
> achieved with Zuul.
> Spring Security will also be extended to use a Knox SSO authenticator.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
