[
https://issues.apache.org/jira/browse/KNOX-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995875#comment-13995875
]
Larry McCay commented on KNOX-364:
----------------------------------
The implementation should ensure that it accommodates both usecases.
There should be no reason that they require separate mechanisms or code.
Kerberos is either required to propagate the effective identity to the cluster
or it isn't.
This jira is really a requirement of KNOX-115 rather than a separate effort.
No kerberos configuration is an example of a certain type of JAAS configuration.
I just want to be careful that we don't end up with two separate knobs that
need to be tweaked.
Kerberos is either on or off - when it is on, it can be configured differently
per topology.
> knox to support mix of secure and non secure clusters
> -----------------------------------------------------
>
> Key: KNOX-364
> URL: https://issues.apache.org/jira/browse/KNOX-364
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.5.0
> Reporter: Dilli Arumugam
> Assignee: Dilli Arumugam
> Fix For: 0.5.0
>
>
> At present (Knox 0.4), all the clusters fronted by a Knox instance have to
> be either secure (secured with Keberos) or non secure. In other words, you
> can not have a mix of secure and non secure clusters.
> This Jira proposes adding support for mix of secure and non secure clusters
> by a single Knox instance
--
This message was sent by Atlassian JIRA
(v6.2#6252)
