[
https://issues.apache.org/jira/browse/RANGER-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang resolved RANGER-1713.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
> Hive testConnection failed after used ldap authentication in Hive.
> ------------------------------------------------------------------
>
> Key: RANGER-1713
> URL: https://issues.apache.org/jira/browse/RANGER-1713
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: master
> Reporter: Qiang Zhang
> Assignee: Qiang Zhang
> Fix For: 1.0.0
>
> Attachments:
> 0001-RANGER-1713-Hive-testConnection-failed-after-open-ld.patch,
> HiveTestConnectionFailAfterLDAP.png
>
>
> Hive testConnection failed after open ldap authentication in Hive.
> Scenarios
> 1.when Hive used SIIMPLE authentication testConnection is ok.
> 2.When Hive used LDAP authentication testConnection is failed.
> Modify Hive-site.xml
> <property>
> <name>hive.server2.authentication</name>
> <value>LDAP</value>
> </property>
> <property>
> <name>hive.server2.authentication.ldap.url</name>
> <value>ldap://192.168.10.101 ldap://192.168.10.102</value>
> <description>
> LDAP connection URL
> </description>
> </property><property>
> <name>hive.server2.authentication.ldap.baseDN</name>
> <value>ou=People,dc=hive,dc=com</value>
> <description>
> LDAP base DN
> </description>
> </property>
> Result:
> Unable to retrieve any files using given parameters, You can still save the
> repository and start creating policies, but you would not be able to use
> autocomplete for resource names. Check ranger_admin.log for more info.
> org.apache.ranger.plugin.client.HadoopException: Unable to connect to Hive
> Thrift Server instance.. Unable to connect to Hive Thrift Server instance..
> Could not open client transport with JDBC Uri:
> jdbc:hive2://10.43.182.241:10000: Peer indicated failure: Error validating
> the login. Peer indicated failure: Error validating the login.
> 3.Reason: Connection parameter password is incorrect .(Do not need to
> undertake the MD5 encryption password).
> 4.Solution: Use MD5 PasswordUtils decryption password.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
