Looks like user does not have the right access in ranger. ... View more

Ranger KMS and Hive workloads will continue to work even when Ranger is down. They will use the local cache of ranger policies downloaded from Ranger. Each plugin pulls the policies periodically (default 30 sec) from Ranger. *** If you found this answer addressed your question, please take a moment to login and click the "accept" link on the answer. ... View more

Delete the entry for "J10001" in x_db_version_h table (in Ranger DB) and restart Ranger. ... View more

Looks like is nimbus/sandbox-hdp.hortonworks.com@HORTONWORKS.COM not getting translated into storm. You need to investigate why. Can you check your jaas config and auth to local rules again? Also the core-site.xml property should be hadoop.proxyuser.<component>.groups. Check for the typo, seems like "s" is missing in your config. ... View more

Hi: Ranger usersync syncs users from various sources to make these users available during security policy authoring via Ranger UI. At the time of resource access, enforcement of policies is performed by Ranger plugins which depend on the actual service (for example HiveServer2 in case of Hive plugin, HDFS Namenode in case of HDFS plugin) to pass the identity of the user and the groups they belong to. To answer your question, sync source used for ranger usersync does not really affect the actual access enforcement. As long as the users in your text file are consistent with the real user source (LDAP/Unix or AD), ranger policies will work fine. Hope this helps. ... View more