[jira] [Commented] (HIVE-11653) Beeline asks for password even when connecting with Kerberos
[ https://issues.apache.org/jira/browse/HIVE-11653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353937#comment-15353937 ] Vihang Karajgaonkar commented on HIVE-11653: HIVE-14062 already fixes this issue. > Beeline asks for password even when connecting with Kerberos > > > Key: HIVE-11653 > URL: https://issues.apache.org/jira/browse/HIVE-11653 > Project: Hive > Issue Type: Bug > Components: Beeline >Affects Versions: 0.14.0, 1.0.1, 1.2.1, 2.0.0 > Environment: Kerberos and Hive >Reporter: Loïc C. Chanel >Assignee: Oleksiy Sayankin > Attachments: HIVE-11653.1.patch > > > When connecting to HiveServer via Beeline, Beeline asks for a password even > if Kerberos is enabled and there is a ticket in cache (kinit have been > successfully executed, as klist shows the ticket is in cache). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11653) Beeline asks for password even when connecting with Kerberos
[ https://issues.apache.org/jira/browse/HIVE-11653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115492#comment-15115492 ] Hive QA commented on HIVE-11653: Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12784136/HIVE-11653.1.patch {color:red}ERROR:{color} -1 due to no test(s) being added or modified. {color:red}ERROR:{color} -1 due to 7 failed/errored test(s), 10029 tests executed *Failed tests:* {noformat} TestHWISessionManager - did not produce a TEST-*.xml file org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_authorization_uri_import org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.createTable org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.insertOverwriteCreate org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.testLockRetryLimit org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.updateSelectUpdate org.apache.hive.jdbc.TestSSL.testSSLVersion {noformat} Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/6732/testReport Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/6732/console Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-6732/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase Tests exited with: TestsFailedException: 7 tests failed {noformat} This message is automatically generated. ATTACHMENT ID: 12784136 - PreCommit-HIVE-TRUNK-Build > Beeline asks for password even when connecting with Kerberos > > > Key: HIVE-11653 > URL: https://issues.apache.org/jira/browse/HIVE-11653 > Project: Hive > Issue Type: Bug > Components: Beeline >Affects Versions: 0.14.0, 1.0.1, 1.2.1, 2.0.0 > Environment: Kerberos and Hive >Reporter: Loïc C. Chanel >Assignee: Oleksiy Sayankin > Attachments: HIVE-11653.1.patch > > > When connecting to HiveServer via Beeline, Beeline asks for a password even > if Kerberos is enabled and there is a ticket in cache (kinit have been > successfully executed, as klist shows the ticket is in cache). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11653) Beeline asks for password even when connecting with Kerberos
[ https://issues.apache.org/jira/browse/HIVE-11653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026655#comment-15026655 ] Arpan commented on HIVE-11653: -- For now workaround is : pass -p "" argument. You will not need to enter the username and password. $> beeline WARNING: Use "yarn jar" to launch YARN applications. Beeline version 1.2.1.2.3.2.0-2950 by Apache Hive *beeline> !connect jdbc:hive2://:1/default;principal=hive/@ -p ""* Connecting to jdbc:hive2://:1/default;principal=hive/@ Connected to: Apache Hive (version 1.2.1.2.3.2.0-2950) Driver: Hive JDBC (version 1.2.1.2.3.2.0-2950) Transaction isolation: TRANSACTION_REPEATABLE_READ 0: jdbc:hive2://> show databases; | database_name | | default| 1 row selected (0.299 seconds) > Beeline asks for password even when connecting with Kerberos > > > Key: HIVE-11653 > URL: https://issues.apache.org/jira/browse/HIVE-11653 > Project: Hive > Issue Type: Bug > Components: Beeline >Affects Versions: 0.14.0 > Environment: Kerberos and Hive >Reporter: Loïc C. Chanel > > When connecting to HiveServer via Beeline, Beeline asks for a password even > if Kerberos is enabled and there is a ticket in cache (kinit have been > successfully executed, as klist shows the ticket is in cache). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11653) Beeline asks for password even when connecting with Kerberos
[ https://issues.apache.org/jira/browse/HIVE-11653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14714510#comment-14714510 ] Lars Francke commented on HIVE-11653: - I think I'd like to take a stab at this if it's alright with you? I've been annoyed by this ever since beeline was introduced :) We need to make a decision on what we want to do though. We could just ignore it if a user doesn't provide username and password. If Hive is configured to accept it it'll fail with an authentication error anyway. On the other hand it provides a way to not pass in the password in a way that ends up in the history or on screen. Any ideas on how to best handle this? > Beeline asks for password even when connecting with Kerberos > > > Key: HIVE-11653 > URL: https://issues.apache.org/jira/browse/HIVE-11653 > Project: Hive > Issue Type: Bug > Components: Beeline >Affects Versions: 0.14.0 > Environment: Kerberos and Hive >Reporter: Loïc C. Chanel > > When connecting to HiveServer via Beeline, Beeline asks for a password even > if Kerberos is enabled and there is a ticket in cache (kinit have been > successfully executed, as klist shows the ticket is in cache). -- This message was sent by Atlassian JIRA (v6.3.4#6332)