Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-6711

FSNamesystem#getAclStatus does not write to the audit log.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: 3.0.0, 2.4.0
    • Fix Version/s: None
    • Component/s: namenode
    • Labels:
      None

      Description

      Consider writing an event to the audit log for the getAclStatus method.

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Resolved Resolved
          117d 22h 40m 1 Chris Nauroth 14/Nov/14 19:51
          Chris Nauroth made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Duplicate [ 3 ]
          Hide
          Chris Nauroth added a comment -

          This was fixed in HDFS-7218, so I'm resolving this as duplicate.

          Show
          Chris Nauroth added a comment - This was fixed in HDFS-7218 , so I'm resolving this as duplicate.
          Chris Nauroth made changes -
          Link This issue duplicates HDFS-7218 [ HDFS-7218 ]
          Hide
          Chris Nauroth added a comment -

          I'm linking this to HDFS-5730, which seeks to make the audit logging policy consistent across all APIs. The decisions in that issue will influence our choice for how to fix this bug.

          Show
          Chris Nauroth added a comment - I'm linking this to HDFS-5730 , which seeks to make the audit logging policy consistent across all APIs. The decisions in that issue will influence our choice for how to fix this bug.
          Chris Nauroth made changes -
          Link This issue relates to HDFS-5730 [ HDFS-5730 ]
          Chris Nauroth made changes -
          Link This issue relates to HDFS-5799 [ HDFS-5799 ]
          Chris Nauroth made changes -
          Field Original Value New Value
          Link This issue relates to HDFS-4685 [ HDFS-4685 ]
          Hide
          Chris Nauroth added a comment -

          We need to confirm what is expected behavior for a read-only operation with respect to the audit log. This appears to be inconsistent in the code right now. getFileInfo writes to the audit log for both successful calls and access denied. getContentSummary logs only for successful calls, not for access denied. listStatus logs for both successful calls and access denied. listCacheDirectives and listCachePools log for both successful calls and access denied. getXAttrs and listXAttrs log only for access denied.

          Show
          Chris Nauroth added a comment - We need to confirm what is expected behavior for a read-only operation with respect to the audit log. This appears to be inconsistent in the code right now. getFileInfo writes to the audit log for both successful calls and access denied. getContentSummary logs only for successful calls, not for access denied. listStatus logs for both successful calls and access denied. listCacheDirectives and listCachePools log for both successful calls and access denied. getXAttrs and listXAttrs log only for access denied.
          Chris Nauroth created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Chris Nauroth
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development