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

Elytron Audit Logging's event timestamp lacks information about seconds

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker 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

      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.

        1. deployment.war
          4 kB
        2. standalone.xml
          27 kB

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

              Created:
              Updated:
              Resolved: