[
https://issues.apache.org/jira/browse/PHOENIX-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617606#comment-16617606
]
ASF GitHub Bot commented on PHOENIX-4688:
-----------------------------------------
Github user pu239ppy commented on the issue:
https://github.com/apache/phoenix/pull/307
@zhouwei0914 This PR is no longer active, please see #344
However here is a quick recap of the issue: It has been relatively easy to
rewrite python-phoenixdb to use requests, however we found out that during
authentication requests-kerberos sends a kerberos OID rather then a SPNEGO OID
for mechanism. There were two workarounds
1. Patch requests-kerberos (was never merged requests-kerberos#115 )
2. A new SPNEGO handler for Avatica that would override Jetty's default
handler (CALCITE-1922)
It turned out that 2 Produced the desired effect that I abandoned the path
of attempting to path requests-kerberos. However in the current PR #344 on top
of Phoenix 5 it appears that this strategy no longer works. See additional
details in later comments in PHOENIX-4688
> Add kerberos authentication to python-phoenixdb
> -----------------------------------------------
>
> Key: PHOENIX-4688
> URL: https://issues.apache.org/jira/browse/PHOENIX-4688
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Lev Bronshtein
> Priority: Minor
>
> In its current state python-phoenixdv does not support support kerberos
> authentication. Using a modern python http library such as requests or
> urllib it would be simple (if not trivial) to add this support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
