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

I finaly found the root cause of this issue, it happens when users connect to ambari web ui and the stay connected for a while then the session is killed due to timeout. In my configuration there are no timeout for :   user.inactivity.timeout.default, user.inactivity.timeout.role.readonly.default   Setting these properties allows ambari to logout users after a period of inactivity.   This error may occurs also when we restart the ambari-server, users still connected with a 401 error message i'm closing this thread and opening a new one with more details about the issue https://community.cloudera.com/t5/Support-Questions/Logout-ambari-s-connected-users-on-ambari-server-restart/td-p/321322 ... View more