[
https://issues.apache.org/jira/browse/PHOENIX-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679923#comment-16679923
]
Biju Nair commented on PHOENIX-5006:
------------------------------------
Thanks [~elserj] for the response. As I mentioned in the comment, having a
{{site.xml}} with the property {{hadoop.security.authentication}} set to
{{Kerberos}} picks up the users Kerberos ticket. But passing it in the property
for the JDBC connection doesn't.
```
prop.setProperty("hadoop.security.authentication","Kerberos");
prop.setProperty("hbase.security.authentication","Kerberos");
prop.setProperty("hbase.master.kerberos.principal","hbase/_HOST@"+krbRealm);
prop.setProperty("hbase.regionserver.kerberos.principal","hbase/_HOST@"+krbRealm);Connection
conn = DriverManager.getConnection("jdbc:phoenix:"+zk+":2181:/hbase",prop)
```
> jdbc connection to secure cluster should be able to use Kerberos ticket of
> user
> -------------------------------------------------------------------------------
>
> Key: PHOENIX-5006
> URL: https://issues.apache.org/jira/browse/PHOENIX-5006
> Project: Phoenix
> Issue Type: Bug
> Reporter: Biju Nair
> Priority: Minor
>
> Currently JDBC connection against a secure Phoenix cluster requires a
> Kerberos principal and keytab to be passed in as part of the connection
> string. But in many instances users may not have a {{Keytab}} especially
> during development. It would be good to support using the logged in users
> Kerberos ticket.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
