Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-54088

Log audit events for user creation

    Details

    • Similar Issues:
    • Epic Link:

      Description

      Using the events defined in JENKINS-54086, the following events should be logged to the audit log:

      • In HudsonPrivateSecurityRealm.createAccount, we should log this account userid.
        • In order to support logging this without directly logging it from Jenkins Core, we'll need to create a new extension point either similar to or based on SecurityListener to notify listeners of an account creation event.

        Attachments

          Activity

          jvz Matt Sicker created issue -
          jvz Matt Sicker made changes -
          Field Original Value New Value
          Epic Link JENKINS-54082 [ 194705 ]
          jvz Matt Sicker made changes -
          Description Using the events defined in JENKINS-54086, the following events should be logged to the audit log:

          * In HudsonPrivateSecurityRealm.createAccount, we should log this account userid.
          Using the events defined in JENKINS-54086, the following events should be logged to the audit log:
           * In HudsonPrivateSecurityRealm.createAccount, we should log this account userid.
           ** In order to support logging this without directly logging it from Jenkins Core, we'll need to create a new extension point either similar to or based on SecurityListener to notify listeners of an account creation event.
          Hide
          mide David Olorundare added a comment - - edited

          I'm looking into this ticket

           

          Show
          mide David Olorundare added a comment - - edited I'm looking into this ticket  
          jvz Matt Sicker made changes -
          Labels audit-logging newbie-friendly audit-logging
          jvz Matt Sicker made changes -
          Component/s audit-log-plugin [ 24638 ]
          Component/s core [ 15593 ]
          mide David Olorundare made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          mide David Olorundare made changes -
          Assignee David Olorundare [ mide ]
          jvz Matt Sicker made changes -
          Rank Ranked lower
          mide David Olorundare made changes -
          Assignee David Olorundare [ mide ]
          mide David Olorundare made changes -
          Status In Progress [ 3 ] Open [ 1 ]
          mide David Olorundare made changes -
          Rank Ranked lower
          mide David Olorundare made changes -
          Assignee David Olorundare [ mide ]
          mide David Olorundare made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          mide David Olorundare made changes -
          Status In Progress [ 3 ] Open [ 1 ]
          mide David Olorundare made changes -
          Assignee David Olorundare [ mide ]
          mide David Olorundare made changes -
          Assignee David Olorundare [ mide ]
          mide David Olorundare made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          mide David Olorundare made changes -
          Status In Progress [ 3 ] Open [ 1 ]
          mide David Olorundare made changes -
          Assignee David Olorundare [ mide ]
          mide David Olorundare made changes -
          Assignee David Olorundare [ mide ]
          mide David Olorundare made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          mide David Olorundare made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          mide David Olorundare made changes -
          Status In Review [ 10005 ] In Progress [ 3 ]
          mide David Olorundare made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          Hide
          jvz Matt Sicker added a comment -

          Changes merged to master, but we're still using a snapshot version of Jenkins to consume the API changes. Do you think we should create a follow up ticket to update the jenkins version here when the upstream PR is merged and released? Or should we just leave this ticket open in review?

          Show
          jvz Matt Sicker added a comment - Changes merged to master, but we're still using a snapshot version of Jenkins to consume the API changes. Do you think we should create a follow up ticket to update the jenkins version here when the upstream PR is merged and released? Or should we just leave this ticket open in review?
          Hide
          mide David Olorundare added a comment -

          follow-up ticket would be good. I just created one. JENKINS-55489

          Show
          mide David Olorundare added a comment - follow-up ticket would be good. I just created one. JENKINS-55489
          Hide
          jvz Matt Sicker added a comment -

          Merged to master, new ticket made for cleaning up the snapshot stuff.

          Show
          jvz Matt Sicker added a comment - Merged to master, new ticket made for cleaning up the snapshot stuff.
          jvz Matt Sicker made changes -
          Status In Review [ 10005 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              mide David Olorundare
              Reporter:
              jvz Matt Sicker
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: