[jira] [Work logged] (HIVE-21538) Beeline: password source though the console reader did not pass to connection param

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-21538?focusedWorklogId=610329&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-610329 ]

ASF GitHub Bot logged work on HIVE-21538:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Jun/21 07:39
            Start Date: 14/Jun/21 07:39
    Worklog Time Spent: 10m 
      Work Description: chjgan opened a new pull request #2386:
URL: https://github.com/apache/hive/pull/2386


   …ot pass to connection param (Rajkumar Singh via Thejas Nair)
   
   Signed-off-by: Ashutosh Chauhan <ha...@apache.org>
   
   (cherry picked from commit 8f7f5d17a7c8bcdd6b019f822c98c2ecb1bba735)
   
   HIVE-25199:beeline -u url -n username -p prompt input password hiveserver always get “anonymous” not the real input password
   
   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/Hive/HowToContribute
     2. Ensure that you have created an issue on the Hive project JIRA: https://issues.apache.org/jira/projects/HIVE/summary
     3. Ensure you have added or run the appropriate tests for your PR: 
     4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]HIVE-XXXXX:  Your PR title ...'.
     5. Be sure to keep the PR description updated to reflect all changes.
     6. Please write your PR title to summarize what this PR proposes.
     7. If possible, provide a concise example to reproduce the issue for a faster review.
   
   -->
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description, screenshot and/or a reproducable example to show the behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to the released Hive versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible.
   If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why it was difficult to add.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 610329)
    Remaining Estimate: 0h
            Time Spent: 10m

> Beeline: password source though the console reader did not pass to connection param
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-21538
>                 URL: https://issues.apache.org/jira/browse/HIVE-21538
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 3.1.0
>         Environment: Hive-3.1 auth set to LDAP
>            Reporter: Rajkumar Singh
>            Assignee: Rajkumar Singh
>            Priority: Major
>             Fix For: 4.0.0
>
>         Attachments: HIVE-21538.01.patch, HIVE-21538.02.patch, HIVE-21538.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Beeline: password source through the console reader do not pass to connection param, this will yield into the Authentication failure in case of LDAP authentication.
> {code}
> beeline -n USER -u "jdbc:hive2://host:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2" -p
> Connecting to jdbc:hive2://host:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2;user=USER
> Enter password for jdbc:hive2://host:2181/: ************
> 19/03/26 19:49:44 [main]: WARN jdbc.HiveConnection: Failed to connect to host:10000
> 19/03/26 19:49:44 [main]: ERROR jdbc.Utils: Unable to read HiveServer2 configs from ZooKeeper
> Unknown HS2 problem when communicating with Thrift server.
> Error: Could not open client transport for any of the Server URI's in ZooKeeper: Peer indicated failure: PLAIN auth failed: javax.security.sasl.AuthenticationException: Error validating LDAP user [Caused by javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580]] (state=08S01,code=0)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)