[
https://issues.apache.org/jira/browse/METRON-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605124#comment-16605124
]
ASF GitHub Bot commented on METRON-1668:
----------------------------------------
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/1112
@mmiklavc the knoxsso is enabled with a toggle in the mpack, to follow the
pattern for NiFi, Ranger and Atlas etc. There is a kind of failover of auth
methods: knoxsso, ldap, nothing in our case. Many of the API calls require auth
because they use username to load settings in the rest backend. As such I’m not
sure no-auth makes sense, but maybe a default to anon would allow @rmerriman’s
use case of dev runs, I’d still say that was a case for a mock backend though,
in angular rather than rest.
> 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)
