Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2625

Elytron Audit Logging's event timestamp lacks information about seconds

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 3.0.0.Beta14
    • None
    • None
    • None
    • Hide
      • Add user via add-user.sh (as Application User)
      • Start server with attached configuration
      • Deploy attached war (containing servlet secured with BASIC HTTP auth)
      • Access http://127.0.0.1:8080/protected/printRoles in a browser
      • Fill in username and password provided in add-user.sh script
      • Compare JBOSS_HOME/standalone/log/elytron-audit.log to JBOSS_HOME/standalone/log/management-audit.log
      Show
      Add user via add-user.sh (as Application User) Start server with attached configuration Deploy attached war (containing servlet secured with BASIC HTTP auth) Access http://127.0.0.1:8080/protected/printRoles in a browser Fill in username and password provided in add-user.sh script Compare JBOSS_HOME/standalone/log/elytron-audit.log to JBOSS_HOME/standalone/log/management-audit.log

    Description

      The format of Elytron Audit Logging's event timestamp is insufficient. It lacks the information about seconds which might be a problem in an environment with thousands of active users.
      Furthermore the format of timestamp is inconsistent with the one used in Management Audit Logging:

      Elytron Audit Logging:

      2/22/17 9:08 AM

      Management Audit Logging:

      2017-02-22 09:08:00

      Suggestions for improvement:
      Use the same format of timestamp in Elytron Audit Logging as is already used in Management Audit Logging.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9019 Elytron Audit Logging's event timestamp lacks information about seconds

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2755 Elytron Audit Logging: rotating-file-audit-log's event timestamp lacks information about seconds

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            People

              yborgess1@redhat.com Yeray Borges Santana
              jtymel Jan Tymel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: