[jira] [Created] (HIVE-28454) The document's description of `PAM` authentication seems outdated

["Qiheng He (Jira)" <ji...@apache.org>]

Qiheng He created HIVE-28454:
--------------------------------

             Summary: The document's description of `PAM` authentication seems outdated
                 Key: HIVE-28454
                 URL: https://issues.apache.org/jira/browse/HIVE-28454
             Project: Hive
          Issue Type: Improvement
            Reporter: Qiheng He


* The document's description of *PAM* authentication seems outdated. I am referring to [https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2#SettingUpHiveServer2-PluggableAuthenticationModules(PAM]) and [https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-JDBCClientSetupforaSecureCluster] .
 * Both documents mention that for HiveServer2 JDBC Driver that connects to HiveServer2 via {*}PAM{*}, we only need to carry the account and password in the jdbc parameters. But the problem is that the *Uber JAR* of *HiveServer2 JDBC Driver* actively excludes {*}JPAM{*}. See [https://github.com/apache/hive/blob/rel/release-4.0.0/jdbc/pom.xml#L286] .

{code:xml}
 <exclude>net.java.dev.jets3t:*</exclude>
<exclude>net.sf.jpam:*</exclude>
<exclude>net.sf.opencsv:*</exclude>
{code}
 - It sounds like users have to at least actively introduce *JPAM* jar in the Maven project?
 - What's even more strange is that isn't there a more modern {*}PAM Java Client{*}? I noticed that the *net.sf.jpam:jpam* used by apache/hive was last released in June 2007. See [https://jpam.sourceforge.net/] and [Maven Central: net.sf.jpam:jpam:1.1 (sonatype.com)|https://central.sonatype.com/artifact/net.sf.jpam/jpam/1.1] .

{code:none}
Latest News
8 June 2007: JPAM 1.1 released
This is a maintenance release which fixes issue 1707044 where JPAM causes JDK crashes on lots of machines. The fix is to roll back the 1.0 fix for expired accounts.
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)