Member since
01-19-2017
3679
Posts
632
Kudos Received
372
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 839 | 06-04-2025 11:36 PM | |
| 1415 | 03-23-2025 05:23 AM | |
| 707 | 03-17-2025 10:18 AM | |
| 2522 | 03-05-2025 01:34 PM | |
| 1650 | 03-03-2025 01:09 PM |
11-14-2017
10:09 AM
@raouia Please can you check this link Configuring Kerberos Authentication for Hue
... View more
11-13-2017
03:11 PM
@raouia To validate the hue kerberos ticket as hue user run.What the output of the below statement? $ klist Forcefully expire the ticket $kdestroy As hue user grab a Kerberos ticket $ kinit -k -t /etc/security/keytabs/hue.service.keytab hue/$FQDN@REALM Validate by running $klist Retry the earlier steps
... View more
11-10-2017
04:03 PM
@Kaliyug Antagonist Did you have a look at this document
... View more
11-09-2017
09:57 PM
1 Kudo
@Jalender The user_permission command shows all access permissions for the current user for a given table: user_permission <table> hbase> user_permission
hbase> user_permission '@ns1'
hbase> user_permission '@.*'
hbase> user_permission '@^[a-c].*'
hbase> user_permission 'table1'
hbase> user_permission 'namespace1:table1'
hbase> user_permission '.*'
hbase> user_permission '^[A-C].*' hbase reference
... View more
11-09-2017
05:13 PM
@Larry Wilson There is a solution for exactly the same issue already posted in HCC have a look at this link https://community.hortonworks.com/questions/122795/sandbox-cannot-open-a-hive-connection-with-connect.html# That should help
... View more
11-08-2017
09:35 PM
@Larry Wilson FYI mine is a single node HDP 2.6 kerberized cluster not a sandbox Can you upload or what the error in /var/log/hive/hiveserver2.log
... View more
11-08-2017
08:50 PM
@Larry Wilson I have a 2.6 single node kerberized cluster but I would think the setup should be the same. Could you attach here the screenshot of the File view config in the Manage Ambari UI
... View more
11-02-2017
10:43 PM
@suraj l Policy name error I noted that you have a policy name proxy instead of /proxy see attached screenshot NiFi supports user authentication via client certificates, via username/password, or via Apache Knox., Username/password authentication is performed by a Login Identity Provider which is a pluggable mechanism for authenticating users via their username/password it is configured in the nifi.properties file options are LDAP and Kerberos. The nifi.login.identity.provider.configuration.file=/usr/hdf/current/nifi/conf/login-identity-providers.xml property specifies the configuration file for Login Identity Providers. The nifi.security.user.login.identity.provider = property indicates which of the configured Login Identity Provider should be used. By default, this property is not configured meaning that username/password must be explicitly enabled. Anonymous users Can you edit /etc/nifi/3.0.1.1-5/0/authorizers.xml change the below property from default true to false <property name="Allow Anonymous">true</property> Please test and revert
... View more
11-02-2017
02:13 PM
@suraj l You are right those files ain't in the /usr/hdf/current/nifi/conf no need to generate them because they are encapsulated in the authorizers.xml <authorizer>
<identifier>ranger-provider</identifier>
<class>org.apache.nifi.authorization.FileAuthorizer</class>
<property name="Authorizations File">/var/lib/nifi/conf/authorizations.xml</property>
<property name="Users File">/var/lib/nifi/conf/users.xml</property>
<property name="Initial Admin Identity"></property>
<property name="Legacy Authorized Users File"></property> So you should check the values in those files in /var/lib/nifi/conf
... View more