[
https://issues.apache.org/jira/browse/METRON-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549274#comment-16549274
]
ASF GitHub Bot commented on METRON-1668:
----------------------------------------
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/1112
In the case of non-SSO ldap auth, there is a login form, it's just embedded
in the spring bits instead of the angular bits. It's not as pretty, but we
could add a login.jsp to make it exactly the same experience (but with a lower
angular maintenance surface).
In the SSO scenario, Knox provides a login form, so we don't need or want
one in the angular app.
In the direct api access scenario, you could provide a bearer token for SSO
with a jwt, or for non-SSO you would just provide basic auth creds and that
would auth against LDAP.
So, you can still provide creds, through either a token, or a browser based
form in all scenarios.
> 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
> 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)
