Try using an hbase-site.xml (on both HBase server and presto-phoenix client) with the following properties: hbase.security.authentication (set to ‘kerberos’), hadoop.security.authentication (set to ‘kerberos’), hbase.regionserver.kerberos.principal, hbase.regionserver.keytab.file, hbase.master.kerberos.principal,hbase.master.keytab.file. You also need to make sure krb5.conf is in the right place for your OS, or else start the Presto jvm with -Djava.security.krb5.conf=
On Thu, Aug 15, 2019 at 7:31 AM Vasileios Dimakopoulos < vasileios.dimakopou...@cern.ch> wrote: > Dear Phoenix Development Team, > > I am Big Data Engineer at CERN and we deployed presto as part of our tests > to create an abstract SQL layer on top of our data sources and backends > (HDFS, HBase, Relational Databases, Kafka, etc). In order to query HBase we > have also deployed successfully Phoenix and the missing puzzle piece to > the abstraction is integrating Phoenix with Presto. However we face some > issues which mainly stem from Kerberos authentication, impersonation and in > general with the delegation of the token. Therefore I would like to ask you > if the Phoenix connector could support a secure HBase cluster and if this > is the case could you guide us or give us any insight on achieving that? > > Thank you in advance. > > Vasileios Dimakopoulos > > CERN Big Data Engineer / Electrical & Computer Engineer > > ----------------------------------------------------------------------------- > Secondary email: vdimakopou...@isc.tuc.gr > LinkedIn<https://www.linkedin.com/in/vassilis-dimakopoulos/> >
