@phr1 You can identify to which resource paths the user was granted access to via Ranger HDFS policies using the following REST API, # curl -k -u <user> https://<ranger-admin-fqdn>:<port>/service/plugins/policies/service/name/<name>?user=<user> Refer "GET /plugins/policies/service/name/{name}" in the following documentation ServiceREST API ... View more

Hi @gianluca , If you would like to view all the attributes while creating a new entity in the Atlas Web UI, please use the toggle button on the top right in the Create entity window to switch it from "Required" to "All".   Hope this helps with your requirement!   Thanks, Prashanth Vishnu ... View more

Hi @arturbrandys1,   The Audit decision taken by Ranger (whether to audit or not) are based on matching resource. That is, if there is a policy which allows audit for a certain resource, then audit will be performed irrespective of whether that policy is governing access policy or not. And in your case, suppose if there is another policy with audit enabled on a higher level - like the root directory "/" for hdfs - then lower level policy can override the access rights but can’t limit the audit logging.   Thanks, Prashanth Vishnu ... View more

Hi @MikeB ,   Here's the latest documentation on how to change the JDK version for Ambari 2.7.5, https://docs.cloudera.com/HDPDocuments/Ambari-latest/administering-ambari/content/amb_change_your_jdk.html   As instructed, after running Ambari server setup, you'll need to restart Ambari server followed by restarting all the cluster services since it is required to restart each component for the new JDK to be used by the Hadoop services.   Hope this helps answer your query! Thanks, Prashanth Vishnu ... View more