[
https://issues.apache.org/jira/browse/METRON-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605084#comment-16605084
]
ASF GitHub Bot commented on METRON-1668:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1112
To @merrimanr 's point, can we provide a config flag to disable auth
altogether, if desired? Maybe an Ambari config dropdown?, e.g. "NONE, KNOX
SSO." Not sure what your plan is with the Ambari config in 1664, but I think
that making SSO enabled/disabled as configurable like we do with Kerberos would
be desirable. I realize there's very likely config and properties to deal with
as supplied by Knox when setting it up in Ambari. I just don't know off the top
of my head how much is automated (again, like Kerberos across the entire
cluster) vs what's ad-hoc and per-component/service. Thoughts?
> Remove login services and screens from UIs
> ------------------------------------------
>
> Key: METRON-1668
> URL: https://issues.apache.org/jira/browse/METRON-1668
> Project: Metron
> Issue Type: Sub-task
> Reporter: Simon Elliston Ball
> Assignee: Simon Elliston Ball
> Priority: Major
>
> Once we have integrated SSO, there is no need for the front-end apps to
> present a login screen, we should remove these from the load footprint.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
