You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 8, 2019. It is now read-only.
Current implementation of Hannibal only works with non kerberized cluster. In a kerberized environment Hannibal service can't talk to secure Hbase. A thought to fix this is:
Create a hannibal user during installation.
A keytab for this new user will be required
Logic to renew tickets for Hannibal will have to be developed
The text was updated successfully, but these errors were encountered:
Some issues it would appear with Hannibal are needing to update the Play WebService API calls[1,2,3] to do SPNEGO authentication.
Perhaps, we can set the Hannibal configuration file to accept a keytab and have Hannibal orchestrate the ticket renewals or if we run Hannibal as the HBase user instead of nobody, we may leverage the HBase tickets already present on the machine for now.
Lastly, in sentric/hannibal#19 there is discussion of Hannibal possibly working on a kerberized cluster as well. Perhaps there are some lessons we can take from there.
Current implementation of
Hannibal
only works with nonkerberized
cluster. In akerberized
environmentHannibal
service can't talk to secureHbase
. A thought to fix this is:hannibal
user during installation.keytab
for this new user will be requiredHannibal
will have to be developedThe text was updated successfully, but these errors were encountered: