[
https://issues.apache.org/jira/browse/METRON-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986825#comment-15986825
]
ASF GitHub Bot commented on METRON-896:
---------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/553
To elaborate on the regression comment:
The vagrant Kerberos steps have all the manual steps added back in. They
should largely be removed, barring any profiler ACL setup.
The manual Kerberos setup is fine (or should be), and can pretty much be
left as-is.
Like I said above, IMO we move the Ambari Kerberos to the same level and
just make any notes regarding the dev environments specifically.
> Document Having Kerberos Issue Renewable Tickets
> ------------------------------------------------
>
> Key: METRON-896
> URL: https://issues.apache.org/jira/browse/METRON-896
> Project: Metron
> Issue Type: Bug
> Reporter: Justin Leet
> Assignee: Justin Leet
>
> Apparently in some circumstances, a default kerberos install on CentOS7 will
> not be configured to issue renewable keytabs. This causes issues with
> deploying topologies.
> Add documentation for both initial setup, as well as allowing a principal to
> get renewable tickets if the KDC is already setup.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
