You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Dilli Arumugam (JIRA)" <ji...@apache.org> on 2013/09/06 18:06:51 UTC

[jira] [Commented] (KNOX-113) Move config to enable Kerberos to the per cluster topology

    [ https://issues.apache.org/jira/browse/KNOX-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760305#comment-13760305 ] 

Dilli Arumugam commented on KNOX-113:
-------------------------------------

We would be able to toggle kerberos on/off individually per topology without much effort if other krb5/jass configuration properties remain same across topologies. We would need more investigation to support different krb5 confgurations across topologies.

                
> Move config to enable Kerberos to the per cluster topology
> ----------------------------------------------------------
>
>                 Key: KNOX-113
>                 URL: https://issues.apache.org/jira/browse/KNOX-113
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.3.0
>            Reporter: Kevin Minder
>             Fix For: 0.4.0
>
>
> Currently the switch to turn Kerberos on or off is is gateway-site.xml.  This setting should really be in the topology files so that one cluster could be secured via kerberos and another using pseudo security.  Understandably there can only be one Kerberos configuration so that information must remain in gateway-site.xml at least until we figure out how to avoid using system properties to configure JAAS/KRB.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira