Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-8124

[Broker-J][REST] Sucessfully authenticated user is reported as <<UNKNOWN>> in ACL operational logs when checking access to management

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • qpid-java-broker-7.0.2, qpid-java-broker-7.0.0, qpid-java-broker-7.0.1
    • qpid-java-broker-7.0.3
    • Broker-J
    • None

    Description

      When user is successfully authenticated, the user information in operational log for checking management access is reported as <<UNKNOWN>> for both Allowed and Denied outcomes:

      INFO  [qtp1675859208-228] (q.m.a.denied) - <<UNKNOWN>> ACL-1002 : Denied : Access Management 
      INFO  [qtp1675859208-64] (q.m.a.allowed) - <<UNKNOWN>> ACL-1001 : Allowed : Access Management 
      INFO  [qtp1675859208-64] (q.m.m.open) - [mng:nyXoe7Io(admin@/127.0.0.1:45666)] MNG-1007 : Open : User admin
      

      As result, it is impossible to identify the principal name of authenticated user in operational log when access is denied.

      Thought, it is possible to get the principal name for "allowed" outcome by looking into the following logs from the same thread, it would be beneficial to print the real principal information in the log for Allowed outcome.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            orudyy Alex Rudyy
            orudyy Alex Rudyy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment