[
https://issues.apache.org/jira/browse/METRON-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707257#comment-16707257
]
ASF GitHub Bot commented on METRON-1895:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1281
Pluggability came up a few times in the dev discussion. Would you be able
to give a brief runthrough of what would be involved in a using choosing to
plugin another option?
In addition, some of the configs are "knox.sso.<blah>". Is there a way to
at least generalize some of this for SSO, or does it have to be Knox specific?
Or can some of it be what Knox specifically requires, while leaving some of it
more general?
These seem like they're fairly tied into things like
`WebSecurityConfig.java`, which makes me wonder how pluggable this is, or if
someone looking to implement something else has to dive fairly deep into source
code to be able to plug something else they choose in.
> Add Knox SSO as an option in Metron
> -----------------------------------
>
> Key: METRON-1895
> URL: https://issues.apache.org/jira/browse/METRON-1895
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
> Priority: Major
>
> This feature will enable accessing Metron REST and the UIs through Knox's SSO
> mechanism.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
