Member since
03-04-2016
165
Posts
35
Kudos Received
7
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1716 | 06-20-2017 03:08 PM | |
8891 | 05-11-2017 09:59 AM | |
8916 | 01-12-2017 01:50 PM | |
1300 | 10-26-2016 03:02 PM | |
5345 | 09-06-2016 07:40 AM |
06-02-2016
01:00 PM
Hi, Ranger is not creating repositories for services (Knox, Kafka). I am using HDP 2.3 I am using default settings. I only installed second Ranger Admin. What can be the issue? Nothing in logs @EDIT If I add them manually, it is not working. Not even logs in audit->plugins that I added new policy.
... View more
Labels:
- Labels:
-
Apache Knox
-
Apache Ranger
05-25-2016
10:16 AM
1 Kudo
@Smart Solutions You can delete users and groups by doing this: log into the ranger database, and delete
the following rows in order. delete from x_group_users where
added_by_id in (1,2) delete from x_user where added_by_id in
(1,2) delete from x_group where added_by_id in
(1,2) Then you can sync your users/groups again with your restrictions.
... View more
05-11-2016
07:24 PM
I found the solution. If anyone else is facing the same problem, review this link and use @bsaini topology. Thanks!
... View more
05-11-2016
06:57 PM
Thank you very much @Alex Miller for your quick response. According to doc that you linked and log I found out that I had misconfigured userDnTemplate. I have another problem. In my AD/LDAP I am using sAMAccountName to identify user, so I need to type at the begging of userDnTemplate something like: sAMAccountName={0},ou=... so on, but it does not recognize users. I cant use cn={0} because as a cn I use two separate words - so I will not work. I dont use uid, and I am not AD admin to add or edit anything.
... View more
05-11-2016
02:28 PM
1 Kudo
Hi,
I have a problem with configuring LDAP/AD with Knox. The DEMO LDAP works great for both: sandbox and my own cluster. I am configuring LDAP connection using this document: Setting Up LDAP Authentication. I configured main.ldapRealm.userDnTemplate and main.ldapRealm.contextFactory.url. I tried both classes in main.ldapRealm (KnoxLdapRealm and Jndi...) I am using Ambari to make changes. The versions I use is: sandbox - 2.4.0 and my cluster 2.3.2. When I configure my LDAP - Knox keeps saying that I am unauthorized (401). The credentials are correct because I can use them to log in beeline which is also configured with LDAP + AD. Do I need to change Advanced users-ldif section in Ambari as well? Thank you in advance.
... View more
Labels:
- Labels:
-
Apache Knox
04-11-2016
10:36 AM
Ambari overwrites the configs in xml files. You need to use Ambari to add those properties (and make any changes in the configuration in the future)
... View more
04-04-2016
08:30 PM
guys, do you have any ideas why I don't have option Oozie-server after clicking +Add button? I tried on every host in my cluster. I am using HDP 2.3 with Ambari 2.1.1
... View more
04-04-2016
04:06 PM
1 Kudo
Hi, My question is what are advantages of using High Availability in Ranger Admin? The only advantage is that I can log in to Ranger Admin GUI from 2 hosts, are there any others?
... View more
Labels:
- Labels:
-
Apache Ranger
03-23-2016
07:58 AM
1 Kudo
Is there a possibility to access beeline via LDAP+AD without providing the password? Any password-less connection is supported? I do not want to type my password everytime I want to get access to Beeline when I use "su" or opening more than one connection on the same host. Thank you in advance
... View more
Labels:
- Labels:
-
Apache Hive
03-11-2016
10:02 AM
Hi, I have exactly the same problem. I have done everything like Adi wrote and still got LDAP 49/52e. I can log in to ldapadmin using the same credentials as beeline rejects the authenticate.
... View more
- « Previous
- Next »